From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dongli Zhang <dongli.zhang@oracle.com>
Subject: [PATCH v2 0/3] KVM: VMX: MSR intercept/passthrough cleanup and simplification
Date: Fri, 23 Feb 2024 12:21:01 -0800 [thread overview]
Message-ID: <20240223202104.3330974-1-seanjc@google.com> (raw)
Clean up VMX's MSR passthrough code, in particular the portion that deals with
userspace MSR filters (KVM needs to force interception if userspace wants to
intercept even if KVM wants to passthrough). As pointed out by Dongli, KVM
does a linear walk twice in quick succession, which is wasteful, confuing, and
unnecessarily brittle.
Same exact idea as Dongli's v1[*], just a different approach to cleaning up the
API for dealing with MSR filters.
v2: Combine "check and get" into a single API instead of adding an out param.
Dongli Zhang (2):
KVM: VMX: fix comment to add LBR to passthrough MSRs
KVM: VMX: return early if msr_bitmap is not supported
Sean Christopherson (1):
KVM: VMX: Combine "check" and "get" APIs for passthrough MSR lookups
arch/x86/kvm/vmx/vmx.c | 68 ++++++++++++++++++------------------------
1 file changed, 29 insertions(+), 39 deletions(-)
base-commit: ec1e3d33557babed2c2c2c7da6e84293c2f56f58
--
2.44.0.rc0.258.g7320e95886-goog
next reply other threads:[~2024-02-23 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:21 Sean Christopherson [this message]
2024-02-23 20:21 ` [PATCH v2 1/3] KVM: VMX: fix comment to add LBR to passthrough MSRs Sean Christopherson
2024-02-23 20:21 ` [PATCH v2 2/3] KVM: VMX: return early if msr_bitmap is not supported Sean Christopherson
2024-02-23 20:21 ` [PATCH v2 3/3] KVM: VMX: Combine "check" and "get" APIs for passthrough MSR lookups Sean Christopherson
2024-02-24 3:14 ` Dongli Zhang
2024-02-24 3:18 ` Dongli Zhang
2024-02-27 21:28 ` [PATCH v2 0/3] KVM: VMX: MSR intercept/passthrough cleanup and simplification Sean Christopherson
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=20240223202104.3330974-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=dongli.zhang@oracle.com \
--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
all inboxes | Powered by JetHome®