From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH] KVM: nVMX: expose VPID capability to L1 Date: Mon, 28 Sep 2015 14:05:18 +0200 Message-ID: <56092CFE.6070801@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Bandan Das , Wincy Van , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Wanpeng Li Return-path: Received: from mail-wi0-f181.google.com ([209.85.212.181]:37429 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755966AbbI1MFU (ORCPT ); Mon, 28 Sep 2015 08:05:20 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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. Paolo