From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Feng Wu <feng.wu@intel.com>,
Dongxiao Xu <dongxiao.xu@intel.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: fix SMEP and SMAP without EPT
Date: Tue, 3 Nov 2015 10:45:01 +0100 [thread overview]
Message-ID: <5638821D.6070701@redhat.com> (raw)
In-Reply-To: <1446499200-17836-1-git-send-email-rkrcmar@redhat.com>
On 02/11/2015 22:20, Radim Krčmář wrote:
> The comment in code had it mostly right, but we enable paging for
> emulated real mode regardless of EPT.
>
> Without EPT (which implies emulated real mode), secondary VCPUs won't
> start unless we disable SM[AE]P when the guest doesn't use paging.
>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
> ---
> arch/x86/kvm/vmx.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index b680c2e0e8a3..ab598558a7a4 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -3788,20 +3788,21 @@ static int vmx_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4)
> if (!is_paging(vcpu)) {
> hw_cr4 &= ~X86_CR4_PAE;
> hw_cr4 |= X86_CR4_PSE;
> - /*
> - * SMEP/SMAP is disabled if CPU is in non-paging mode
> - * in hardware. However KVM always uses paging mode to
> - * emulate guest non-paging mode with TDP.
> - * To emulate this behavior, SMEP/SMAP needs to be
> - * manually disabled when guest switches to non-paging
> - * mode.
> - */
> - hw_cr4 &= ~(X86_CR4_SMEP | X86_CR4_SMAP);
> } else if (!(cr4 & X86_CR4_PAE)) {
> hw_cr4 &= ~X86_CR4_PAE;
> }
> }
>
> + if (!enable_unrestricted_guest && !is_paging(vcpu))
> + /*
> + * SMEP/SMAP is disabled if CPU is in non-paging mode in
> + * hardware. However KVM always uses paging mode without
> + * unrestricted guest.
> + * To emulate this behavior, SMEP/SMAP needs to be manually
> + * disabled when guest switches to non-paging mode.
> + */
> + hw_cr4 &= ~(X86_CR4_SMEP | X86_CR4_SMAP);
> +
> vmcs_writel(CR4_READ_SHADOW, cr4);
> vmcs_writel(GUEST_CR4, hw_cr4);
> return 0;
>
Applied with Cc: stable@vger.kernel.org.
Paolo
prev parent reply other threads:[~2015-11-03 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 21:20 [PATCH] KVM: VMX: fix SMEP and SMAP without EPT Radim Krčmář
2015-11-03 9:45 ` 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=5638821D.6070701@redhat.com \
--to=pbonzini@redhat.com \
--cc=dongxiao.xu@intel.com \
--cc=feng.wu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).