Re: [PATCH v2] KVM: Avoid zapping unrelated shadows in __kvm_set_memory_region()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 04/14/2012 12:33 AM, Marcelo Tosatti wrote:
> mmio sptes are not related to any particular slot (by definition),
> i think you misunderstood the purpose of this flush. It handles
>
> 1) [start, end] gpa range unmapped.
> 2) mmio sptes are created that map this range.
> 3) a new slot is created. mmio sptes that map [start, end] range,
> which is now backed by new memslot should be removed.
>
> Perhaps there is an efficient way to clear all mmio sptes, or all
> mmio sptes pointing to [start, end] (instead of all sptes), here.

It shouldn't be too hard for direct maps.  For indirect maps, there is
now way to reach the spte, since we can't rmap mmio sptes.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[KVM ARM]     [KVM ia64]     [KVM ppc]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux