From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2 8/9] KVM: x86, SVM: isolate vcpu->arch.dr6 from vmcb->save.dr6
Date: Fri, 8 May 2020 11:32:10 -0400 [thread overview]
Message-ID: <20200508153210.GZ228260@xz-x1> (raw)
In-Reply-To: <dd8eb45b-4556-6aaa-0061-11b9124020b1@redhat.com>
On Fri, May 08, 2020 at 12:33:57AM +0200, Paolo Bonzini wrote:
> On 07/05/20 21:28, Peter Xu wrote:
> >> - svm->vcpu.arch.dr6 = dr6;
> >> + WARN_ON(svm->vcpu.arch.switch_db_regs & KVM_DEBUGREG_WONT_EXIT);
> >> + svm->vcpu.arch.dr6 &= ~(DR_TRAP_BITS | DR6_RTM);
> >> + svm->vcpu.arch.dr6 |= dr6 & ~DR6_FIXED_1;
> > I failed to figure out what the above calculation is going to do...
>
> The calculation is merging the cause of the #DB with the guest DR6.
> It's basically the same effect as kvm_deliver_exception_payload. The
> payload has DR6_RTM flipped compared to DR6, so you have the following
> simplfications:
>
> payload = (dr6 ^ DR6_RTM) & ~DR6_FIXED_1;
> /* This is kvm_deliver_exception_payload: */
> vcpu->arch.dr6 &= ~DR_TRAP_BITS;
> vcpu->arch.dr6 |= DR6_RTM;
> /* copy dr6 bits other than RTM */
> vcpu->arch.dr6 |= payload;
> /* copy flipped RTM bit */
> vcpu->arch.dr6 ^= payload & DR6_RTM;
>
> ->
>
> payload = (dr6 ^ DR6_RTM) & ~DR6_FIXED_1;
> /* clear RTM here, so that we can OR it below */
> vcpu->arch.dr6 &= ~(DR_TRAP_BITS | DR6_RTM);
> /* copy dr6 bits other than RTM */
> vcpu->arch.dr6 |= payload & ~DR6_RTM;
> /* copy flipped RTM bit */
> vcpu->arch.dr6 |= (payload ^ DR6_RTM) & DR6_RTM;
>
> ->
>
> /* we can drop the double XOR of DR6_RTM */
> dr6 &= ~DR6_FIXED_1;
> vcpu->arch.dr6 &= ~(DR_TRAP_BITS | DR6_RTM);
> vcpu->arch.dr6 |= dr6 & ~DR6_RTM;
> vcpu->arch.dr6 |= dr6 & DR6_RTM;
>
> ->
>
> /* we can do the two ORs with a single operation */
> vcpu->arch.dr6 &= ~(DR_TRAP_BITS | DR6_RTM);
> vcpu->arch.dr6 |= dr6 & ~DR6_FIXED_1;
Oh that's quite some math. :) Thanks Paolo!
Shall we introduce a helper for both kvm_deliver_exception_payload and here
(e.g. kvm_merge_dr6)? Also, wondering whether this could be a bit easier to
follow by defining:
/*
* These bits could be kept being set until the next #DB if not
* explicitly cleared.
*/
#define DR6_CARRY_OVER_BITS (DR6_BT | DR6_BS | DR6_BD)
Then the imho above calculation could also become:
vcpu->arch.dr6 = (vcpu->arch.dr6 & DR6_CARRY_OVER_BITS) | save.dr6;
What do you think?
>
> > E.g., I
> > think the old "BT|BS|BD" bits in the old arch.dr6 cache will be leftover even
> > if none of them is set in save.dr6, while we shouldn't?
>
> Those bits should be kept; this is covered for example by the "hw
> breakpoint (test that dr6.BS is not cleared)" testcase in kvm-unit-tests
> x86/debug.c.
Right. Thanks!
--
Peter Xu
next prev parent reply other threads:[~2020-05-08 15:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 11:50 [PATCH v2 0/9] KVM_SET_GUEST_DEBUG tests and fixes, DR accessors cleanups Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 1/9] KVM: X86: Declare KVM_CAP_SET_GUEST_DEBUG properly Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 2/9] KVM: x86: fix DR6 delivery for various cases of #DB injection Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 3/9] KVM: X86: Set RTM for DB_VECTOR too for KVM_EXIT_DEBUG Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 4/9] KVM: X86: Fix single-step with KVM_SET_GUEST_DEBUG Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 5/9] KVM: selftests: Add KVM_SET_GUEST_DEBUG test Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 6/9] KVM: nSVM: trap #DB and #BP to userspace if guest debugging is on Paolo Bonzini
2020-05-07 18:22 ` Peter Xu
2020-05-07 11:50 ` [PATCH v2 7/9] KVM: SVM: keep DR6 synchronized with vcpu->arch.dr6 Paolo Bonzini
2020-05-07 18:22 ` Peter Xu
2020-05-07 22:21 ` Paolo Bonzini
2020-05-07 11:50 ` [PATCH v2 8/9] KVM: x86, SVM: isolate vcpu->arch.dr6 from vmcb->save.dr6 Paolo Bonzini
2020-05-07 19:28 ` Peter Xu
2020-05-07 22:33 ` Paolo Bonzini
2020-05-08 15:32 ` Peter Xu [this message]
2020-05-09 13:28 ` Paolo Bonzini
2020-05-11 16:15 ` Peter Xu
2020-05-07 11:50 ` [PATCH 9/9] KVM: VMX: pass correct DR6 for GD userspace exit Paolo Bonzini
2020-05-07 16:18 ` Peter Xu
2020-05-07 16:21 ` Paolo Bonzini
2020-05-07 16:38 ` Peter Xu
2020-05-07 17:42 ` Paolo Bonzini
2020-05-07 18:05 ` Peter Xu
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=20200508153210.GZ228260@xz-x1 \
--to=peterx@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).