From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>, Wanpeng Li <kernellwp@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"kvm list" <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH 1/2] KVM: VMX: Don't expose unrestricted_guest is enabled if ept is disabled
Date: Mon, 9 Oct 2017 09:54:17 +0200 [thread overview]
Message-ID: <f3c2f655-8d1c-05a6-b311-47491cc55c2e@redhat.com> (raw)
In-Reply-To: <CALMp9eQiYNYHcDDXVpsuKdO6KeQxptbvW4xRktYDbL90f=j9eQ@mail.gmail.com>
On 09/10/2017 00:35, Jim Mattson wrote:
> If it were me, I'd apply De Morgan to that expression, but the logic looks fine.
>
> Reviewed-by: Jim Mattson <jmattson@google.com>
I'm okay with the way Wanpeng wrote it, but as a follow up this:
if (!cpu_has_vmx_ept() ||
!cpu_has_vmx_ept_4levels() ||
!cpu_has_vmx_ept_mt_wb()) {
enable_ept = 0;
enable_unrestricted_guest = 0;
enable_ept_ad_bits = 0;
}
can be reduced to just "enable_ept = 0".
Paolo
> On Sat, Oct 7, 2017 at 7:35 PM, Wanpeng Li <kernellwp@gmail.com> wrote:
>> From: Wanpeng Li <wanpeng.li@hotmail.com>
>>
>> SDM mentioned:
>>
>> "If either the “unrestricted guest” VM-execution control or the “mode-based
>> execute control for EPT” VM- execution control is 1, the “enable EPT”
>> VM-execution control must also be 1."
>>
>> However, we can still observe unrestricted_guest is Y after inserting the kvm-intel.ko
>> w/ ept=N. It depends on later starts a guest in order that the function
>> vmx_compute_secondary_exec_control() can be executed, then both the module parameter
>> and exec control fields will be amended.
>>
>> This patch fixes it by amending module parameter immediately during vmcs data setup.
>>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Radim Krčmář <rkrcmar@redhat.com>
>> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
>> ---
>> arch/x86/kvm/vmx.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>> index 244e366..3e664ca 100644
>> --- a/arch/x86/kvm/vmx.c
>> +++ b/arch/x86/kvm/vmx.c
>> @@ -6737,7 +6737,7 @@ static __init int hardware_setup(void)
>> if (!cpu_has_vmx_ept_ad_bits() || !enable_ept)
>> enable_ept_ad_bits = 0;
>>
>> - if (!cpu_has_vmx_unrestricted_guest())
>> + if (!cpu_has_vmx_unrestricted_guest() || !enable_ept)
>> enable_unrestricted_guest = 0;
>>
>> if (!cpu_has_vmx_flexpriority())
>> --
>> 2.7.4
>>
prev parent reply other threads:[~2017-10-09 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 2:35 Wanpeng Li
2017-10-08 2:35 ` [PATCH 2/2] KVM: X86: XCR0 should be set to the fixed value on vCPU reset Wanpeng Li
2017-10-08 22:36 ` Jim Mattson
2017-10-09 8:04 ` Paolo Bonzini
2017-10-08 22:35 ` [PATCH 1/2] KVM: VMX: Don't expose unrestricted_guest is enabled if ept is disabled Jim Mattson
2017-10-09 7:54 ` Paolo Bonzini [this message]
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=f3c2f655-8d1c-05a6-b311-47491cc55c2e@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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
all inboxes | Powered by JetHome®