kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>, kvm@vger.kernel.org
Cc: jmattson@google.com, seanjc@google.com
Subject: Re: [PATCH 0/4 v5] nSVM: Test host RFLAGS.TF on VMRUN
Date: Fri, 26 Mar 2021 18:35:52 +0100	[thread overview]
Message-ID: <474b77d4-ef2c-507c-201a-d22f9e6567cf@redhat.com> (raw)
In-Reply-To: <20210323175006.73249-1-krish.sadhukhan@oracle.com>

On 23/03/21 18:50, Krish Sadhukhan wrote:
> v4 -> v5:
>          1. The fix in patch# 1 has been modified. We are queue'ing the
>             pending #DB intercept via nested_svm_vmexit() if the VMRUN is
>             found to be single-stepped.
>          2. In patch# 3, the assembly label for tracking the VMRUN RIP has
>             been changed to u64* from void*.
> 
> [PATCH 1/4 v5] KVM: nSVM: If VMRUN is single-stepped, queue the #DB
> [PATCH 2/4 v5] KVM: X86: Add a utility function to read current RIP
> [PATCH 3/4 v5] KVM: nSVM: Add assembly label to VMRUN instruction
> [PATCH 4/4 v5] nSVM: Test effect of host RFLAGS.TF on VMRUN
> 
>   arch/x86/kvm/svm/nested.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 
> Krish Sadhukhan (1):
>        KVM: nSVM: If VMRUN is single-stepped, queue the #DB intercept in nested_svm_vmexit()
> 
>   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
> 

Queued 1-3-4, 2 is not needed.

Paolo


      parent reply	other threads:[~2021-03-26 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 17:50 [PATCH 0/4 v5] nSVM: Test host RFLAGS.TF on VMRUN Krish Sadhukhan
2021-03-23 17:50 ` [PATCH 1/4 v5] KVM: nSVM: If VMRUN is single-stepped, queue the #DB intercept in nested_svm_vmexit() Krish Sadhukhan
2021-03-26 17:32   ` Paolo Bonzini
2021-03-30  0:16     ` Krish Sadhukhan
2021-03-23 17:50 ` [PATCH 2/4 v5] KVM: X86: Add a utility function to read current RIP Krish Sadhukhan
2021-03-23 17:50 ` [PATCH 3/4 v5] KVM: nSVM: Add assembly label to VMRUN instruction Krish Sadhukhan
2021-03-23 17:50 ` [PATCH 4/4 v5] nSVM: Test effect of host RFLAGS.TF on VMRUN Krish Sadhukhan
2021-03-26 17:35 ` Paolo Bonzini [this message]

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=474b77d4-ef2c-507c-201a-d22f9e6567cf@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=krish.sadhukhan@oracle.com \
    --cc=kvm@vger.kernel.org \
    --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 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).