From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>, g@char.us.oracle.com
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
David Woodhouse <dwmw@amazon.co.uk>,
KarimAllah Ahmed <karahmed@amazon.de>
Subject: Re: [PATCH] KVM: VMX: expose the host's ARCH_CAPABILITIES MSR to userspace
Date: Mon, 26 Feb 2018 17:23:55 -0500 [thread overview]
Message-ID: <20180226222355.GL22024@char.us.oracle.com> (raw)
In-Reply-To: <20180226221300.GK22024@char.us.oracle.com>
On Mon, Feb 26, 2018 at 05:13:00PM -0500, Konrad Rzeszutek Wilk wrote:
> On Sat, Feb 24, 2018 at 01:52:26AM +0100, Paolo Bonzini wrote:
> > Use the new MSR feature framework to expose the ARCH_CAPABILITIES MSR to
> > userspace. This way, userspace can access the capabilities even if it
> > does not have the permissions to read MSRs.
>
> ... That is good but could you expand a bit of why it would want this?
>
> I am 99% sure it is due to the lovely spectre_v2 mitigation but
> could you include that in the commit message so that in say a year
> folks would know what this is?
>
> Also what branch is this based on? I am not seeing this vmx_get_msr_feature
> in kvm/master or kvm/linux-next ?
Ah I see you posted them! Sorry for that particular noise.
> >
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > ---
> > arch/x86/kvm/vmx.c | 12 +++++++++++-
> > arch/x86/kvm/x86.c | 1 +
> > 2 files changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> > index 130fca0ea1bf..99689061e11e 100644
> > --- a/arch/x86/kvm/vmx.c
> > +++ b/arch/x86/kvm/vmx.c
> > @@ -3228,7 +3228,17 @@ static inline bool vmx_feature_control_msr_valid(struct kvm_vcpu *vcpu,
> >
> > static int vmx_get_msr_feature(struct kvm_msr_entry *msr)
> > {
> > - return 1;
> > + switch (msr->index) {
> > + case MSR_IA32_ARCH_CAPABILITIES:
> > + if (!boot_cpu_has(X86_FEATURE_ARCH_CAPABILITIES))
> > + return 1;
> > + rdmsrl(msr->index, msr->data);
> > + break;
> > + default:
> > + return 1;
> > + }
> > +
> > + return 0;
> > }
> >
> > /*
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index 54b4ed55945b..e9a8cc9e3b2b 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -1054,6 +1054,7 @@ bool kvm_rdpmc(struct kvm_vcpu *vcpu)
> > * can be used by a hypervisor to validate requested CPU features.
> > */
> > static u32 msr_based_features[] = {
> > + MSR_IA32_ARCH_CAPABILITIES,
> > MSR_F10H_DECFG,
> > };
> >
> > --
> > 1.8.3.1
> >
next prev parent reply other threads:[~2018-02-26 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519433546-33879-1-git-send-email-pbonzini@redhat.com>
2018-02-26 22:13 ` [PATCH] KVM: VMX: expose the host's ARCH_CAPABILITIES MSR to userspace Konrad Rzeszutek Wilk
2018-02-26 22:23 ` Konrad Rzeszutek Wilk [this message]
2018-03-01 21:39 ` Radim Krčmář
2018-03-02 9:36 ` Paolo Bonzini
2018-03-02 21:42 ` Radim Krčmář
2018-03-07 11:53 ` Paolo Bonzini
2018-03-07 14:56 ` Radim Krčmář
2018-03-07 15:10 ` Paolo Bonzini
2018-03-07 15:39 ` Radim Krčmář
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=20180226222355.GL22024@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=dwmw@amazon.co.uk \
--cc=g@char.us.oracle.com \
--cc=karahmed@amazon.de \
--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