From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Naveen N Rao <naveen@kernel.org>
Subject: [PATCH v2 4/4] KVM: Isolate apicv_update_lock and apicv_nr_irq_window_req in a cacheline
Date: Fri, 23 Jan 2026 14:45:14 -0800 [thread overview]
Message-ID: <20260123224514.2509129-5-seanjc@google.com> (raw)
In-Reply-To: <20260123224514.2509129-1-seanjc@google.com>
Force apicv_update_lock and apicv_nr_irq_window_req to reside in their own
cacheline to avoid generating significant contention due to false sharing
when KVM is contantly creating IRQ windows. E.g. apicv_inhibit_reasons is
read on every VM-Enter; disabled_exits is read on page faults, on PAUSE
exits, if a vCPU is scheduled out, etc.; kvmclock_offset is read every time
a vCPU needs to refresh kvmclock, and so on and so forth.
Isolating the write-mostly fields from all other (read-mostly) fields
improves performance by 7-8% when running netperf TCP_RR between two guests
on the same physical host when using an in-kernel PIT in re-inject mode.
Reported-by: Naveen N Rao (AMD) <naveen@kernel.org>
Closes: https://lore.kernel.org/all/yrxhngndj37edud6tj5y3vunaf7nirwor4n63yf4275wdocnd3@c77ujgialc6r
Tested-by: Naveen N Rao (AMD) <naveen@kernel.org>
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
arch/x86/include/asm/kvm_host.h | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index b08baeff98b2..8a9f797b6a68 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -1435,13 +1435,23 @@ struct kvm_arch {
bool apic_access_memslot_enabled;
bool apic_access_memslot_inhibited;
+ /*
+ * Force apicv_update_lock and apicv_nr_irq_window_req to reside in a
+ * dedicated cacheline. They are write-mostly, whereas most everything
+ * else in kvm_arch is read-mostly. Note that apicv_inhibit_reasons is
+ * read-mostly: toggling VM-wide inhibits is rare; _checking_ for
+ * inhibits is common.
+ */
+ ____cacheline_aligned
/*
* Protects apicv_inhibit_reasons and apicv_nr_irq_window_req (with an
* asterisk, see kvm_inc_or_dec_irq_window_inhibit() for details).
*/
struct rw_semaphore apicv_update_lock;
- unsigned long apicv_inhibit_reasons;
atomic_t apicv_nr_irq_window_req;
+ ____cacheline_aligned
+
+ unsigned long apicv_inhibit_reasons;
gpa_t wall_clock;
--
2.52.0.457.g6b5491de43-goog
next prev parent reply other threads:[~2026-01-23 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 22:45 [PATCH v2 0/4] KVM: SVM: Fix IRQ window inhibit handling Sean Christopherson
2026-01-23 22:45 ` [PATCH v2 1/4] KVM: SVM: Fix clearing IRQ window inhibit with nested guests Sean Christopherson
2026-01-23 22:45 ` [PATCH v2 2/4] KVM: SVM: Fix IRQ window inhibit handling across multiple vCPUs Sean Christopherson
2026-01-23 22:45 ` [PATCH v2 3/4] KVM: SVM: Optimize IRQ window inhibit handling Sean Christopherson
2026-01-23 22:45 ` Sean Christopherson [this message]
2026-03-05 17:08 ` [PATCH v2 0/4] KVM: SVM: Fix " 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=20260123224514.2509129-5-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen@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