Re: [PATCH v2] KVM: MMU: Don't flush shadow when enabling dirty tracking

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

 



On Mon, 27 Dec 2010 12:43:59 +0200
Avi Kivity <avi@xxxxxxxxxx> wrote:
> rmap_write_protect() protects a 4k page, so it uses update_spte() to 
> drop the W bit, and drops large mappings that point to the same 4k 
> page.  We can't drop the W bit from the large page, because that will 
> write protect 511 unrelated pages.

I see, I'll reread these from that sense.

Thank you for the explanation.

  Takuya

> 
> > I may be able to learn something from your share code later on.
> >
> 
> Unlikely - I was thinking of sharing the
> 
> >  +				drop_spte(kvm,&pt[i],
> >  +					  shadow_trap_nonpresent_pte);
> >  +				--kvm->stat.lpages;
> 
> 
> bits.  Now I'm thinking of dropping kvm->stat, I think we have all the 
> information it provides covered by tracepoints.
> 
> -- 
--
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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux