From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: [PATCH 0/3] KVM: x86: cleanup and fixes for debug register accesses
Date: Tue, 5 May 2020 13:36:15 +0200 [thread overview]
Message-ID: <d09671ef-0a9d-c854-7715-d3077e09e734@redhat.com> (raw)
In-Reply-To: <20200504234904.GG6299@xz-x1>
On 05/05/20 01:49, Peter Xu wrote:
>> The guest debugging test would basically cover the gdbstub case, which
>> is different from kvm-unit-tests. It would run similar tests to
>> kvm-unit-tests, but #DB and #BP exceptions would be replaced by
>> KVM_EXIT_DEBUG, and MOVs to DR would be replaced by KVM_SET_GUEST_DEBUG.
>>
>> It could also cover exception payload support in KVM_GET_VCPU_EVENTS,
>> but that is more complicated because it would require support for
>> exceptions in the selftests.
>
> Yep, I guess the in-guest debug test will still need the exception support,
> though I also guess we don't need that when we have the kvm unit test
We can still use it in order to test for example live migration with
pending debug exceptions (KVM_GET_VCPU_EVENTS), but it's less important
indeed.
Paolo
prev parent reply other threads:[~2020-05-05 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:55 [PATCH 0/3] KVM: x86: cleanup and fixes for debug register accesses Paolo Bonzini
2020-05-04 15:55 ` [PATCH 1/3] KVM: SVM: fill in kvm_run->debug.arch.dr[67] Paolo Bonzini
2020-05-06 23:42 ` Sasha Levin
2020-05-04 15:55 ` [PATCH 2/3] KVM: SVM: keep DR6 synchronized with vcpu->arch.dr6 Paolo Bonzini
2020-05-04 15:55 ` [PATCH 3/3] KVM: x86: simplify dr6 accessors in kvm_x86_ops Paolo Bonzini
2020-05-04 18:55 ` [PATCH 0/3] KVM: x86: cleanup and fixes for debug register accesses Peter Xu
2020-05-04 19:20 ` Paolo Bonzini
2020-05-04 23:49 ` Peter Xu
2020-05-05 11:36 ` 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=d09671ef-0a9d-c854-7715-d3077e09e734@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 \
/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).