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,
Mathias Krause <minipli@grsecurity.net>
Subject: [PATCH 0/2] KVM: x86: Cleanup kvm_get_dr() usage
Date: Fri, 9 Feb 2024 14:07:50 -0800 [thread overview]
Message-ID: <20240209220752.388160-1-seanjc@google.com> (raw)
Make kvm_get_dr() use an actual return instead of a void return with an
output, which led to a _lot_ of ugly code, and then open code all direct
reads to DR6 and DR7, as KVM has a goofy mix of some flows open coding
reads and some flows bouncing through kvm_get_dr().
Sean Christopherson (2):
KVM: x86: Make kvm_get_dr() return a value, not use an out parameter
KVM: x86: Open code all direct reads to guest DR6 and DR7
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/emulate.c | 17 ++++-------------
arch/x86/kvm/kvm_emulate.h | 2 +-
arch/x86/kvm/smm.c | 15 ++++-----------
arch/x86/kvm/svm/svm.c | 7 ++-----
arch/x86/kvm/vmx/nested.c | 2 +-
arch/x86/kvm/vmx/vmx.c | 5 +----
arch/x86/kvm/x86.c | 20 +++++++-------------
8 files changed, 21 insertions(+), 49 deletions(-)
base-commit: 873eef46b33c86be414d60bd00390e64fc0f006f
--
2.43.0.687.g38aa6559b0-goog
next reply other threads:[~2024-02-09 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 22:07 Sean Christopherson [this message]
2024-02-09 22:07 ` [PATCH 1/2] KVM: x86: Make kvm_get_dr() return a value, not use an out parameter Sean Christopherson
2024-02-09 22:29 ` Mathias Krause
2024-02-09 22:07 ` [PATCH 2/2] KVM: x86: Open code all direct reads to guest DR6 and DR7 Sean Christopherson
2024-02-09 22:30 ` Mathias Krause
2024-02-23 1:35 ` [PATCH 0/2] KVM: x86: Cleanup kvm_get_dr() usage 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=20240209220752.388160-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@grsecurity.net \
--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®