From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Emanuele Giuseppe Esposito <eesposit@redhat.com>,
kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
Ben Serebrin <serebrin@google.com>,
Peter Shier <pshier@google.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] kvm: vmx: Add IA32_FLUSH_CMD guest support
Date: Fri, 17 Mar 2023 15:53:45 -0700 [thread overview]
Message-ID: <20230317225345.z5chlrursjfbz52o@desk> (raw)
In-Reply-To: <20230317190432.GA863767@dev-arch.thelio-3990X>
On Fri, Mar 17, 2023 at 12:04:32PM -0700, Nathan Chancellor wrote:
> Hi Emanuele,
>
> On Wed, Feb 01, 2023 at 08:29:03AM -0500, Emanuele Giuseppe Esposito wrote:
> > Expose IA32_FLUSH_CMD to the guest if the guest CPUID enumerates
> > support for this MSR. As with IA32_PRED_CMD, permission for
> > unintercepted writes to this MSR will be granted to the guest after
> > the first non-zero write.
> >
> > Signed-off-by: Jim Mattson <jmattson@google.com>
> > Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
> > ---
> > arch/x86/kvm/vmx/nested.c | 3 ++
> > arch/x86/kvm/vmx/vmx.c | 70 +++++++++++++++++++++++++--------------
> > 2 files changed, 48 insertions(+), 25 deletions(-)
> >
> > diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> > index 557b9c468734..075b5ade7c80 100644
> > --- a/arch/x86/kvm/vmx/nested.c
> > +++ b/arch/x86/kvm/vmx/nested.c
> > @@ -654,6 +654,9 @@ static inline bool nested_vmx_prepare_msr_bitmap(struct kvm_vcpu *vcpu,
> > nested_vmx_set_intercept_for_msr(vmx, msr_bitmap_l1, msr_bitmap_l0,
> > MSR_IA32_PRED_CMD, MSR_TYPE_W);
> >
> > + nested_vmx_set_intercept_for_msr(vmx, msr_bitmap_l1, msr_bitmap_l0,
> > + MSR_IA32_FLUSH_CMD, MSR_TYPE_W);
> > +
> > kvm_vcpu_unmap(vcpu, &vmx->nested.msr_bitmap_map, false);
> >
> > vmx->nested.force_msr_bitmap_recalc = false;
> > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> > index c788aa382611..9a78ea96a6d7 100644
> > --- a/arch/x86/kvm/vmx/vmx.c
> > +++ b/arch/x86/kvm/vmx/vmx.c
> > @@ -2133,6 +2133,39 @@ static u64 vmx_get_supported_debugctl(struct kvm_vcpu *vcpu, bool host_initiated
> > return debugctl;
> > }
> >
> > +static int vmx_set_msr_ia32_cmd(struct kvm_vcpu *vcpu,
> > + struct msr_data *msr_info,
> > + bool guest_has_feat, u64 cmd,
> > + int x86_feature_bit)
> > +{
> > + if (!msr_info->host_initiated && !guest_has_feat)
> > + return 1;
> > +
> > + if (!(msr_info->data & ~cmd))
Looks like this is doing a reverse check. Shouldn't this be as below:
---
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index f88578407494..e8d9033559c4 100644
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -2141,7 +2141,7 @@ static int vmx_set_msr_ia32_cmd(struct kvm_vcpu *vcpu,
if (!msr_info->host_initiated && !guest_has_feat)
return 1;
- if (!(msr_info->data & ~cmd))
+ if (msr_info->data & ~cmd)
return 1;
if (!boot_cpu_has(x86_feature_bit))
return 1;
next prev parent reply other threads:[~2023-03-17 22:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:29 [PATCH 0/3] KVM: support the cpu feature FLUSH_L1D Emanuele Giuseppe Esposito
2023-02-01 13:29 ` [PATCH 1/3] kvm: vmx: Add IA32_FLUSH_CMD guest support Emanuele Giuseppe Esposito
2023-03-17 19:04 ` Nathan Chancellor
2023-03-17 22:53 ` Pawan Gupta [this message]
2023-03-17 23:14 ` Nathan Chancellor
2023-03-17 23:59 ` Pawan Gupta
2023-03-20 14:53 ` Sean Christopherson
2023-03-20 15:40 ` Emanuele Giuseppe Esposito
2023-03-20 16:24 ` Sean Christopherson
2023-03-20 16:48 ` Emanuele Giuseppe Esposito
2023-03-21 23:59 ` Sean Christopherson
2023-02-01 13:29 ` [PATCH 2/3] kvm: svm: " Emanuele Giuseppe Esposito
2023-02-01 13:29 ` [PATCH 3/3] kvm: x86: Advertise FLUSH_L1D to user space Emanuele Giuseppe Esposito
2023-03-14 13:29 ` [PATCH 0/3] KVM: support the cpu feature FLUSH_L1D Paolo Bonzini
2023-03-20 16:52 ` Jim Mattson
2023-03-21 8:40 ` Emanuele Giuseppe Esposito
2023-03-21 9:43 ` Paolo Bonzini
2023-03-21 18:30 ` Jim Mattson
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=20230317225345.z5chlrursjfbz52o@desk \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eesposit@redhat.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=nathan@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=seanjc@google.com \
--cc=serebrin@google.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®