From: David Hildenbrand <david@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3 v2] KVM: nVMX: Enable VMFUNC for the L1 hypervisor
Date: Mon, 10 Jul 2017 14:15:01 +0200 [thread overview]
Message-ID: <f04c16e2-8bd7-81cc-5d4c-efb6f367c79f@redhat.com> (raw)
In-Reply-To: <f0267f6f-673c-9175-1140-c9038a0031bc@redhat.com>
On 10.07.2017 13:03, Paolo Bonzini wrote:
>
>
> 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).
>
Thanks, I missed that paragraph.
> Paolo
>
--
Thanks,
David
next prev parent reply other threads:[~2017-07-10 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 23:03 [PATCH 0/3 v2] Expose VMFUNC to the nested hypervisor Bandan Das
2017-07-06 23:03 ` [PATCH 1/3 v2] KVM: vmx: Enable VMFUNCs Bandan Das
2017-07-10 8:54 ` David Hildenbrand
2017-07-10 9:17 ` Paolo Bonzini
2017-07-10 9:20 ` David Hildenbrand
2017-07-10 9:21 ` Paolo Bonzini
2017-07-06 23:03 ` [PATCH 2/3 v2] KVM: nVMX: Enable VMFUNC for the L1 hypervisor Bandan Das
2017-07-10 9:17 ` David Hildenbrand
2017-07-10 11:03 ` Paolo Bonzini
2017-07-10 12:15 ` David Hildenbrand [this message]
2017-07-06 23:03 ` [PATCH 3/3 v2] KVM: nVMX: Emulate EPTP switching " Bandan Das
2017-07-07 8:30 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f04c16e2-8bd7-81cc-5d4c-efb6f367c79f@redhat.com \
--to=david@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome