DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 7C40680F6D
Subject: Re: [PATCH 2/3 v2] KVM: nVMX: Enable VMFUNC for the L1 hypervisor
To: David Hildenbrand <david@redhat.com>, Bandan Das <bsd@redhat.com>,
        kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
References: <20170706230323.29952-1-bsd@redhat.com>
 <20170706230323.29952-3-bsd@redhat.com>
 <afdcb489-fd32-29d5-4072-3c7a65b0f032@redhat.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <f0267f6f-673c-9175-1140-c9038a0031bc@redhat.com>
Date: Mon, 10 Jul 2017 13:03:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <afdcb489-fd32-29d5-4072-3c7a65b0f032@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 680
Lines: 19


On 10/07/2017 11:17, David Hildenbrand wrote:
>> +
>> +	vmcs12 = get_vmcs12(vcpu);
>> +	if ((vmcs12->vm_function_control & (1 << function)) == 0)
> (learned that in c, shifting beyond the type size is undefined)
> 
> Should we check for function < 64 here? (as SDM mentions)

It should be already.  The manual says:

The VMFUNC instruction causes an invalid-opcode exception (#UD) if the
“enable VM functions” VM-execution controls is 0 1 or the value of EAX
is greater than 63 (only VM functions 0–63 can be enable). Otherwise,
the instruction causes a VM exit if the bit at position EAX is 0 in the
VM-function controls (the selected VM function is not enabled).

Paolo