From: Sean Christopherson <seanjc@google.com>
To: Jim Mattson <jmattson@google.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Carlos López" <clopez@suse.de>,
"Maciej W . Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH v3 5/8] KVM: VMX: Prioritize DR7.GD=1 #DB over CPL>0 #GP on Intel
Date: Tue, 16 Jun 2026 10:13:04 -0700 [thread overview]
Message-ID: <ajGEILz_ldZe-Hbq@google.com> (raw)
In-Reply-To: <CALMp9eTc=mUWb15J_px59=LcTEC6Q8ec2UbnkpwBoWhunaeKFw@mail.gmail.com>
On Mon, Jun 15, 2026, Jim Mattson wrote:
> On Fri, Jun 12, 2026 at 4:03 PM Sean Christopherson <seanjc@google.com> wrote:
> > Note, neither Intel's SDM nor AMD's APM says anything about the relative
> > priority, hence the empirical testing. Arguably Intel's description of
> > DR7.GD:
> >
> > causes a debug exception to be generated prior to any MOV instruction
> > that accesses a debug register.
> >
> > implies that DR7.GD has higher priority. But that's a fairly weak argument
> > as the statement would still hold true if the #GP due to CPL>0 had higher
> > priority, as the #GP would prevent any access to a DR.
> >
> > Fixes: 3b88e41a4134 ("KVM: SVM: Add intercept check for accessing dr registers")
> > Signed-off-by: Sean Christopherson <seanjc@google.com>
> > ---
> > arch/x86/kvm/emulate.c | 7 ++++++-
> > arch/x86/kvm/vmx/vmx.c | 6 +++---
> > 2 files changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> > index 127a21eeef66..b4dc57fe0bc9 100644
> > --- a/arch/x86/kvm/emulate.c
> > +++ b/arch/x86/kvm/emulate.c
> > @@ -3834,6 +3834,7 @@ static int check_cr_access(struct x86_emulate_ctxt *ctxt)
> >
> > static int check_dr_read(struct x86_emulate_ctxt *ctxt)
> > {
> > + bool is_intel = ctxt->ops->guest_cpuid_is_intel_compatible(ctxt);
>
> Hmmm...Have you tested VIA?
Nope. I'll loop in the Zhaoxin folks when I post the KVM-Unit-Test code to at
least see what Zhaoxin CPUs do. Zhaoxin is taking over the Centaur CPUID leaves,
so unless someone happens to have access to a VIA CPU, that's probably the best
we can do.
> Or even Hygon? How compatible is "<vendor>_compatible"?
I'm confident Hygon matches AMD, given that Hygon inherited pretty much all of
the Zen errata.
next prev parent reply other threads:[~2026-06-16 17:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 23:01 [PATCH v3 0/8] KVM: x86: Fix emulated MOV DR{4,5} #GP bugs Sean Christopherson
2026-06-12 23:01 ` [PATCH v3 1/8] KVM: x86: Treat any non-zero return from set_dr() as a faulting condition Sean Christopherson
2026-06-15 17:46 ` Jim Mattson
2026-06-12 23:01 ` [PATCH v3 2/8] KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value Sean Christopherson
2026-06-15 17:51 ` Jim Mattson
2026-06-12 23:01 ` [PATCH v3 3/8] KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority Sean Christopherson
2026-06-15 18:04 ` Jim Mattson
2026-06-12 23:01 ` [PATCH v3 4/8] KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL Sean Christopherson
2026-06-15 18:07 ` Jim Mattson
2026-06-12 23:01 ` [PATCH v3 5/8] KVM: VMX: Prioritize DR7.GD=1 #DB over CPL>0 #GP on Intel Sean Christopherson
2026-06-15 18:14 ` Jim Mattson
2026-06-16 17:13 ` Sean Christopherson [this message]
2026-06-12 23:01 ` [PATCH v3 6/8] KVM: x86: Use kvm_dr{6,7}_valid() to check DR{4,5,6,7} write values in emulator Sean Christopherson
2026-06-15 17:24 ` Jim Mattson
2026-06-12 23:01 ` [PATCH v3 7/8] KVM: x86: WARN if MOV DR emulation hits a "too late" #GP Sean Christopherson
2026-06-15 18:30 ` Jim Mattson
2026-06-15 19:08 ` Sean Christopherson
2026-06-12 23:01 ` [PATCH v3 8/8] KVM: x86: Read CR4.DE in emulator if and only if accessing DR4 or DR5 Sean Christopherson
2026-06-15 17:40 ` Jim Mattson
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=ajGEILz_ldZe-Hbq@google.com \
--to=seanjc@google.com \
--cc=clopez@suse.de \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--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