diff options
author | Sean Christopherson <seanjc@google.com> | 2025-04-01 09:34:45 -0700 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2025-04-24 11:19:40 -0700 |
commit | b41f8638b9d30fbe045b4ef83ff4136c56a57397 (patch) | |
tree | ae3a5c8e389d4f02f795e2eeb34266dbe1abc40e /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 06b4d0ea226c295e85a9daa6aed0ae9fa3ff8a94 (diff) |
KVM: VMX: Isolate pure loads from atomic XCHG when processing PIR
Rework KVM's processing of the PIR to use the same algorithm as posted
MSIs, i.e. to do READ(x4) => XCHG(x4) instead of (READ+XCHG)(x4). Given
KVM's long-standing, sub-optimal use of 32-bit accesses to the PIR, it's
safe to say far more thought and investigation was put into handling the
PIR for posted MSIs, i.e. there's no reason to assume KVM's existing
logic is meaningful, let alone superior.
Matching the processing done by posted MSIs will also allow deduplicating
the code between KVM and posted MSIs.
See the comment for handle_pending_pir() added by commit 1b03d82ba15e
("x86/irq: Install posted MSI notification handler") for details on
why isolating loads from XCHG is desirable.
Suggested-by: Jim Mattson <jmattson@google.com>
Link: https://lore.kernel.org/r/20250401163447.846608-7-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions