From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <graf@amazon.com>, kvm list <kvm@vger.kernel.org>
Cc: Aaron Lewis <aaronlewis@google.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
KarimAllah Raslan <karahmed@amazon.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 5/8] KVM: x86: SVM: Prevent MSR passthrough when MSR access is denied
Date: Sat, 26 Sep 2020 00:22:16 +0200 [thread overview]
Message-ID: <f471cac2-89fd-2d61-04fa-2edf6ec438e5@redhat.com> (raw)
In-Reply-To: <20200925143422.21718-6-graf@amazon.com>
On 25/09/20 16:34, Alexander Graf wrote:
> We will introduce the concept of MSRs that may not be handled in kernel
> space soon. Some MSRs are directly passed through to the guest, effectively
> making them handled by KVM from user space's point of view.
>
> This patch introduces all logic required to ensure that MSRs that
> user space wants trapped are not marked as direct access for guests.
>
> Signed-off-by: Alexander Graf <graf@amazon.com>
>
> ---
>
> v7 -> v8:
>
> - s/KVM_MSR_ALLOW/KVM_MSR_FILTER/g
> ---
Ok, just some cosmetic fixes on top:
diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
index bb9f438e9e62..692110f2ac6f 100644
--- a/arch/x86/kvm/svm/svm.c
+++ b/arch/x86/kvm/svm/svm.c
@@ -553,7 +553,7 @@ static int svm_cpu_init(int cpu)
}
-static int direct_access_msr_idx(u32 msr)
+static int direct_access_msr_slot(u32 msr)
{
u32 i;
@@ -561,33 +561,33 @@ static int direct_access_msr_idx(u32 msr)
if (direct_access_msrs[i].index == msr)
return i;
- return -EINVAL;
+ return -ENOENT;
}
static void set_shadow_msr_intercept(struct kvm_vcpu *vcpu, u32 msr, int read,
int write)
{
struct vcpu_svm *svm = to_svm(vcpu);
- int idx = direct_access_msr_idx(msr);
+ int slot = direct_access_msr_slot(msr);
- if (idx == -EINVAL)
+ if (slot == -ENOENT)
return;
/* Set the shadow bitmaps to the desired intercept states */
if (read)
- set_bit(idx, svm->shadow_msr_intercept.read);
+ set_bit(slot, svm->shadow_msr_intercept.read);
else
- clear_bit(idx, svm->shadow_msr_intercept.read);
+ clear_bit(slot, svm->shadow_msr_intercept.read);
if (write)
- set_bit(idx, svm->shadow_msr_intercept.write);
+ set_bit(slot, svm->shadow_msr_intercept.write);
else
- clear_bit(idx, svm->shadow_msr_intercept.write);
+ clear_bit(slot, svm->shadow_msr_intercept.write);
}
static bool valid_msr_intercept(u32 index)
{
- return direct_access_msr_idx(index) != -EINVAL;
+ return direct_access_msr_slot(index) != -ENOENT;
}
static bool msr_write_intercepted(struct kvm_vcpu *vcpu, u32 msr)
@@ -609,7 +609,7 @@ static bool msr_write_intercepted(struct kvm_vcpu *vcpu, u32 msr)
return !!test_bit(bit_write, &tmp);
}
-static void set_msr_interception_nosync(struct kvm_vcpu *vcpu, u32 *msrpm,
+static void set_msr_interception_bitmap(struct kvm_vcpu *vcpu, u32 *msrpm,
u32 msr, int read, int write)
{
u8 bit_read, bit_write;
@@ -646,7 +646,7 @@ static void set_msr_interception(struct kvm_vcpu *vcpu, u32 *msrpm, u32 msr,
int read, int write)
{
set_shadow_msr_intercept(vcpu, msr, read, write);
- set_msr_interception_nosync(vcpu, msrpm, msr, read, write);
+ set_msr_interception_bitmap(vcpu, msrpm, msr, read, write);
}
static u32 *svm_vcpu_alloc_msrpm(void)
@@ -694,7 +694,7 @@ static void svm_msr_filter_changed(struct kvm_vcpu *vcpu)
u32 read = test_bit(i, svm->shadow_msr_intercept.read);
u32 write = test_bit(i, svm->shadow_msr_intercept.write);
- set_msr_interception_nosync(vcpu, svm->msrpm, msr, read, write);
+ set_msr_interception_bitmap(vcpu, svm->msrpm, msr, read, write);
}
}
next prev parent reply other threads:[~2020-09-25 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 14:34 [PATCH v8 0/8] Allow user space to restrict and augment MSR emulation Alexander Graf
2020-09-25 14:34 ` [PATCH v8 1/8] KVM: x86: Return -ENOENT on unimplemented MSRs Alexander Graf
2020-09-25 16:40 ` Jim Mattson
2020-09-25 14:34 ` [PATCH v8 2/8] KVM: x86: Deflect unknown MSR accesses to user space Alexander Graf
2020-09-28 16:05 ` Aaron Lewis
2020-09-25 14:34 ` [PATCH v8 3/8] KVM: x86: Add infrastructure for MSR filtering Alexander Graf
2020-09-28 16:08 ` Aaron Lewis
2020-09-25 14:34 ` [PATCH v8 4/8] KVM: x86: Prepare MSR bitmaps for userspace tracked MSRs Alexander Graf
2020-09-25 14:34 ` [PATCH v8 5/8] KVM: x86: SVM: Prevent MSR passthrough when MSR access is denied Alexander Graf
2020-09-25 22:01 ` Paolo Bonzini
2020-09-25 22:22 ` Paolo Bonzini [this message]
2020-09-25 14:34 ` [PATCH v8 6/8] KVM: x86: VMX: " Alexander Graf
2020-10-02 1:11 ` Peter Xu
2020-10-05 18:43 ` Sean Christopherson
2020-09-25 14:34 ` [PATCH v8 7/8] KVM: x86: Introduce MSR filtering Alexander Graf
2020-09-28 16:09 ` Aaron Lewis
2020-09-25 14:34 ` [PATCH v8 8/8] KVM: selftests: Add test for user space MSR handling Alexander Graf
2020-09-28 16:10 ` Aaron Lewis
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=f471cac2-89fd-2d61-04fa-2edf6ec438e5@redhat.com \
--to=pbonzini@redhat.com \
--cc=aaronlewis@google.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@oracle.com \
--cc=graf@amazon.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).