Messages in this thread | | | Subject | Re: [PATCH] KVM: nVMX: expose VPID capability to L1 | From | Wanpeng Li <> | Date | Tue, 29 Sep 2015 09:15:52 +0800 |
| |
On 9/28/15 8:05 PM, Paolo Bonzini wrote: > > On 24/09/2015 08:51, Wanpeng Li wrote: >> /* >> * For nested guests, we don't do anything specific >> * for single context invalidation. Hence, only advertise >> * support for global context invalidation. >> */ >> - vmx->nested.nested_vmx_ept_caps |= VMX_EPT_EXTENT_GLOBAL_BIT; >> + vmx->nested.nested_vmx_ept_vpid_caps |= VMX_EPT_EXTENT_GLOBAL_BIT; >> + vmx->nested.nested_vmx_ept_vpid_caps |= (unsigned long)vmx_capability.vpid << 32; > Hi Wanpeng, the comment above is about invept, but the same applies > applies to invvpid. We can set only VMX_VPID_EXTENT_GLOBAL_CONTEXT_BIT.
Agreed. I see the patch has already in kvm/queue, if I need to send out another patch or you can adjust it for me? :-)
Regards, Wanpeng Li
| |