From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: [PATCH 0/3] KVM: X86: Two fixes for KVM_SET_GUEST_DEBUG, and a selftest
Date: Wed, 6 May 2020 11:30:33 +0200 [thread overview]
Message-ID: <a16352f2-73ef-b2fa-44e0-82b52dab8466@redhat.com> (raw)
In-Reply-To: <20200505205000.188252-1-peterx@redhat.com>
On 05/05/20 22:49, Peter Xu wrote:
> The first two patches try to fix two issues I found (I think) with the
> selftest. The 3rd patch is the test itself. Note, we need below patches to be
> applied too for the test to work:
>
> KVM: X86: Declare KVM_CAP_SET_GUEST_DEBUG properly
> KVM: selftests: Fix build for evmcs.h
>
> Please review, thanks.
>
> Peter Xu (3):
> KVM: X86: Set RTM for DB_VECTOR too for KVM_EXIT_DEBUG
> KVM: X86: Fix single-step with KVM_SET_GUEST_DEBUG
> KVM: selftests: Add KVM_SET_GUEST_DEBUG test
>
> arch/x86/kvm/vmx/vmx.c | 2 +-
> arch/x86/kvm/x86.c | 2 +-
> tools/testing/selftests/kvm/Makefile | 1 +
> .../testing/selftests/kvm/include/kvm_util.h | 2 +
> tools/testing/selftests/kvm/lib/kvm_util.c | 9 +
> .../testing/selftests/kvm/x86_64/debug_regs.c | 180 ++++++++++++++++++
> 6 files changed, 194 insertions(+), 2 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/x86_64/debug_regs.c
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-05-06 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 20:49 [PATCH 0/3] KVM: X86: Two fixes for KVM_SET_GUEST_DEBUG, and a selftest Peter Xu
2020-05-05 20:49 ` [PATCH 1/3] KVM: X86: Set RTM for DB_VECTOR too for KVM_EXIT_DEBUG Peter Xu
2020-05-05 20:49 ` [PATCH 2/3] KVM: X86: Fix single-step with KVM_SET_GUEST_DEBUG Peter Xu
2020-05-05 20:50 ` [PATCH 3/3] KVM: selftests: Add KVM_SET_GUEST_DEBUG test Peter Xu
2020-05-06 9:30 ` 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=a16352f2-73ef-b2fa-44e0-82b52dab8466@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@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;
as well as URLs for NNTP newsgroup(s).