[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU436-SMTP836B8F64853B13DFF973C804E0@phx.gbl>
Date: Tue, 29 Sep 2015 09:15:52 +0800
From: Wanpeng Li <wanpeng.li@...mail.com>
To: Paolo Bonzini <pbonzini@...hat.com>
CC: Jan Kiszka <jan.kiszka@...mens.com>, Bandan Das <bsd@...hat.com>,
Wincy Van <fanwenyi0529@...il.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: nVMX: expose VPID capability to L1
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists