From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, jmattson@google.com, seanjc@google.com
Subject: [PATCH 0/4 v4] nSVM: Test host RFLAGS.TF on VMRUN
Date: Mon, 22 Mar 2021 14:10:03 -0400 [thread overview]
Message-ID: <20210322181007.71519-1-krish.sadhukhan@oracle.com> (raw)
v3 -> v4:
1. Patch# 1 fixes the problem differently from what v3 did. In the new
fix, svm_vcpu_run() for L1 first checks if the previous #VMEXIT from
L2 was a VMRUN #VMEXIT and if that VMRUN is being single-stepped. If
both of these conditions are satisfied, it synthesizes a #DB
intercept to account for the pending RFLAGS.TF. This prevents the
instruction next to VMRUN from being executed before taking care of
the pending RFLAGS.TF.
2. in Patch# 4, in host_rflags_test(), the call to vmmcall() has been
moved down.
[PATCH 1/4 v4] KVM: nSVM: Trigger synthetic #DB intercept following completion of single-stepped VMRUN instruction
[PATCH 2/4 v4] KVM: X86: Add a utility function to read current RIP
[PATCH 3/4 v4] nSVM: Add assembly label to VMRUN instruction
[PATCH 4/4 v4] nSVM: Test effect of host RFLAGS.TF on VMRUN
arch/x86/kvm/svm/svm.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
Krish Sadhukhan (1):
KVM: Trigger synthetic #DB intercept following completion of single-stepped VMRUN instruction
lib/x86/processor.h | 7 ++++
x86/svm.c | 16 ++++++--
x86/svm_tests.c | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 134 insertions(+), 4 deletions(-)
Krish Sadhukhan (3):
KVM: X86: Add a utility function to read current RIP
KVM: nSVM: Add assembly label to VMRUN instruction
nSVM: Test effect of host RFLAGS.TF on VMRUN
next reply other threads:[~2021-03-22 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 18:10 Krish Sadhukhan [this message]
2021-03-22 18:10 ` [PATCH 1/4 v4] KVM: nSVM: Trigger synthetic #DB intercept following completion of single-stepped VMRUN instruction Krish Sadhukhan
2021-03-22 19:08 ` Paolo Bonzini
2021-03-22 23:24 ` Krish Sadhukhan
2021-03-22 18:10 ` [PATCH 2/4 v4] KVM: X86: Add a utility function to read current RIP Krish Sadhukhan
2021-03-22 18:10 ` [PATCH 3/4 v4] nSVM: Add assembly label to VMRUN instruction Krish Sadhukhan
2021-03-22 19:07 ` Paolo Bonzini
2021-03-22 18:10 ` [PATCH 4/4 v4] nSVM: Test effect of host RFLAGS.TF on VMRUN Krish Sadhukhan
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=20210322181007.71519-1-krish.sadhukhan@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.