diff options
| author | Sean Christopherson <seanjc@google.com> | 2026-06-12 16:01:07 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-07-08 13:41:03 -0700 |
| commit | 55ac576a9bf43b32ef4de926316f3a57f08887e0 (patch) | |
| tree | 1060f815a52af314ce05ef448821126d5373e5dd /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 8f683a4dc546a9ced5dce4b6fb862be26a0572c4 (diff) | |
KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value
When emulating a MOV DR, specifically a write to DR6 or DR7, treat a #DB
due to DR7.GD (General Detect) as higher priority than a #GP due to an
illegal value. While neither Intel's SDM nor AMD's APM says anything
about the relative priority, empirical testing on Intel and AMD shows that
the #DB has higher priority. And for VMX, where the instruction intercept
has priority over *all* exceptions, KVM already treats the #DB as having
higher priority.
Cc: Maciej W. Rozycki <macro@orcam.me.uk>
Fixes: 3b88e41a4134 ("KVM: SVM: Add intercept check for accessing dr registers")
Reviewed-by: Jim Mattson <jmattson@google.com>
Link: https://patch.msgid.link/20260612230113.684301-3-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
