From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Jim Mattson <jmattson@google.com>
Subject: [PATCH v2 0/8] x86/irq: KVM: Optimize KVM's PIR harvesting
Date: Tue, 1 Apr 2025 09:34:39 -0700 [thread overview]
Message-ID: <20250401163447.846608-1-seanjc@google.com> (raw)
Optimizing KVM's PIR harvesting using the same techniques as posted MSIs,
most notably to use 8-byte accesses on 64-bit kernels (/facepalm).
Fix a few warts along the way, and finish up by adding a helper to dedup
the PIR harvesting code between KVM and posted MSIs.
v2:
- Collect a review. [tglx]
- Use an "unsigned long" with a bitwise-OR to gather PIR. [tglx]
v1: https://lore.kernel.org/all/20250315030630.2371712-1-seanjc@google.com
Sean Christopherson (8):
x86/irq: Ensure initial PIR loads are performed exactly once
x86/irq: Track if IRQ was found in PIR during initial loop (to load
PIR vals)
KVM: VMX: Ensure vIRR isn't reloaded at odd times when sync'ing PIR
x86/irq: KVM: Track PIR bitmap as an "unsigned long" array
KVM: VMX: Process PIR using 64-bit accesses on 64-bit kernels
KVM: VMX: Isolate pure loads from atomic XCHG when processing PIR
KVM: VMX: Use arch_xchg() when processing PIR to avoid instrumentation
x86/irq: KVM: Add helper for harvesting PIR to deduplicate KVM and
posted MSIs
arch/x86/include/asm/posted_intr.h | 78 +++++++++++++++++++++++++++---
arch/x86/kernel/irq.c | 63 ++++--------------------
arch/x86/kvm/lapic.c | 20 ++++----
arch/x86/kvm/lapic.h | 4 +-
arch/x86/kvm/vmx/posted_intr.h | 2 +-
5 files changed, 95 insertions(+), 72 deletions(-)
base-commit: 782f9feaa9517caf33186dcdd6b50a8f770ed29b
--
2.49.0.472.ge94155a9ec-goog
next reply other threads:[~2025-04-01 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 16:34 Sean Christopherson [this message]
2025-04-01 16:34 ` [PATCH v2 1/8] x86/irq: Ensure initial PIR loads are performed exactly once Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 2/8] x86/irq: Track if IRQ was found in PIR during initial loop (to load PIR vals) Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 3/8] KVM: VMX: Ensure vIRR isn't reloaded at odd times when sync'ing PIR Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 4/8] x86/irq: KVM: Track PIR bitmap as an "unsigned long" array Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 5/8] KVM: VMX: Process PIR using 64-bit accesses on 64-bit kernels Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 6/8] KVM: VMX: Isolate pure loads from atomic XCHG when processing PIR Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 7/8] KVM: VMX: Use arch_xchg() when processing PIR to avoid instrumentation Sean Christopherson
2025-04-01 16:34 ` [PATCH v2 8/8] x86/irq: KVM: Add helper for harvesting PIR to deduplicate KVM and posted MSIs Sean Christopherson
2025-04-25 23:11 ` [PATCH v2 0/8] x86/irq: KVM: Optimize KVM's PIR harvesting 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=20250401163447.846608-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®