From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Sean Christopherson <seanjc@google.com>
Subject: [kvm-unit-tests PATCH 0/4] x86/debug: Add Bus Lock Detect coverage
Date: Fri, 25 Sep 2026 15:59:59 -0700 [thread overview]
Message-ID: <20260925230003.2362261-1-seanjc@google.com> (raw)
Add Bus Lock Detect #DB coverage to the debug test, along with coverage to
validate the semantics of active-low bits.
Sean Christopherson (4):
x86/debug: Set all active-low DR6 bits when resetting DR6
x86/debug: Run the "debug" test with the host CPU model
x86/debug: Verify that KVM correctly emulates DR6 active-low and
fixed-1 semantics
x86/debug: Add actual test coverage for Bus Lock Detect #DBs
x86/debug.c | 162 +++++++++++++++++++++++++++++++++++-----------
x86/unittests.cfg | 1 +
2 files changed, 125 insertions(+), 38 deletions(-)
base-commit: 5ce4dcd089c1729a66cb318c80b06fd84efee38d
--
2.56.0.rc1.315.gc6ed9934b7-goog
next reply other threads:[~2026-09-25 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 22:59 Sean Christopherson [this message]
2026-09-25 23:00 ` [kvm-unit-tests PATCH 1/4] x86/debug: Set all active-low DR6 bits when resetting DR6 Sean Christopherson
2026-09-25 23:00 ` [kvm-unit-tests PATCH 2/4] x86/debug: Run the "debug" test with the host CPU model Sean Christopherson
2026-09-25 23:00 ` [kvm-unit-tests PATCH 3/4] x86/debug: Verify that KVM correctly emulates DR6 active-low and fixed-1 semantics Sean Christopherson
2026-09-25 23:00 ` [kvm-unit-tests PATCH 4/4] x86/debug: Add actual test coverage for Bus Lock Detect #DBs Sean Christopherson
2026-10-02 21:07 ` [kvm-unit-tests PATCH 0/4] x86/debug: Add Bus Lock Detect coverage Sean Christopherson
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=20260925230003.2362261-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@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