Re: [PATCH 03/11] kvm: x86: Add fast CR3 switch code path

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

 



On 05/07/2018 09:27 AM, Paolo Bonzini wrote:
> Not having KPTI slow down to a crawl without EPT is surely useful, but I
> wonder if this could be generalized a bit, so that for example we don't
> acquire the MMU lock on nested vmentry/vmexit...

Yes, it seems like we may be able to use a similar scheme for L1<->L2 switches. For nested vmexits, we should always be able to use the fast path. For nested vmentries, we could use the fast path if the target CR3/EPTP is the same as the previous one.

Thanks,
Junaid



[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