From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Luigi Rizzo <lrizzo@google.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>
Subject: [patch 2/3] x86/irq: Cleanup posted MSI code
Date: Tue, 25 Nov 2025 11:20:22 +0100 (CET) [thread overview]
Message-ID: <20251125102000.699735132@linutronix.de> (raw)
In-Reply-To: 20251125101912.564125647@linutronix.de
Make code and comments readable.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/kernel/irq.c | 31 +++++++++++++------------------
1 file changed, 13 insertions(+), 18 deletions(-)
--- a/arch/x86/kernel/irq.c
+++ b/arch/x86/kernel/irq.c
@@ -401,11 +401,9 @@ static DEFINE_PER_CPU_CACHE_HOT(bool, po
void intel_posted_msi_init(void)
{
- u32 destination;
- u32 apic_id;
+ u32 destination, apic_id;
this_cpu_write(posted_msi_pi_desc.nv, POSTED_MSI_NOTIFICATION_VECTOR);
-
/*
* APIC destination ID is stored in bit 8:15 while in XAPIC mode.
* VT-d spec. CH 9.11
@@ -449,8 +447,8 @@ static __always_inline bool handle_pendi
}
/*
- * Performance data shows that 3 is good enough to harvest 90+% of the benefit
- * on high IRQ rate workload.
+ * Performance data shows that 3 is good enough to harvest 90+% of the
+ * benefit on high interrupt rate workloads.
*/
#define MAX_POSTED_MSI_COALESCING_LOOP 3
@@ -460,11 +458,8 @@ static __always_inline bool handle_pendi
*/
DEFINE_IDTENTRY_SYSVEC(sysvec_posted_msi_notification)
{
+ struct pi_desc *pid = this_cpu_ptr(&posted_msi_pi_desc);
struct pt_regs *old_regs = set_irq_regs(regs);
- struct pi_desc *pid;
- int i = 0;
-
- pid = this_cpu_ptr(&posted_msi_pi_desc);
/* Mark the handler active for intel_ack_posted_msi_irq() */
this_cpu_write(posted_msi_handler_active, true);
@@ -472,25 +467,25 @@ DEFINE_IDTENTRY_SYSVEC(sysvec_posted_msi
irq_enter();
/*
- * Max coalescing count includes the extra round of handle_pending_pir
- * after clearing the outstanding notification bit. Hence, at most
- * MAX_POSTED_MSI_COALESCING_LOOP - 1 loops are executed here.
+ * Loop only MAX_POSTED_MSI_COALESCING_LOOP - 1 times here to take
+ * the final handle_pending_pir() invocation after clearing the
+ * outstanding notification bit into account.
*/
- while (++i < MAX_POSTED_MSI_COALESCING_LOOP) {
+ for (int i = 1; i < MAX_POSTED_MSI_COALESCING_LOOP; i++) {
if (!handle_pending_pir(pid->pir, regs))
break;
}
/*
- * Clear outstanding notification bit to allow new IRQ notifications,
- * do this last to maximize the window of interrupt coalescing.
+ * Clear the outstanding notification bit to rearm the notification
+ * mechanism.
*/
pi_clear_on(pid);
/*
- * There could be a race of PI notification and the clearing of ON bit,
- * process PIR bits one last time such that handling the new interrupts
- * are not delayed until the next IRQ.
+ * Clearing the ON bit can race with a notification. Process the
+ * PIR bits one last time so that handling the new interrupts is
+ * not delayed until the next notification happens.
*/
handle_pending_pir(pid->pir, regs);
next prev parent reply other threads:[~2025-11-25 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:20 [patch 0/3] x86/irq: Bugfix and cleanup for posted MSI interrupts Thomas Gleixner
2025-11-25 10:20 ` [patch 1/3] x86/msi: Make irq_retrigger() functional for posted MSI Thomas Gleixner
2025-11-25 17:54 ` Luigi Rizzo
2025-11-25 19:04 ` Thomas Gleixner
2025-11-25 10:20 ` Thomas Gleixner [this message]
2025-11-25 10:20 ` [patch 3/3] x86/irq_remapping: Sanitize posted_msi_supported() Thomas Gleixner
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=20251125102000.699735132@linutronix.de \
--to=tglx@linutronix.de \
--cc=baolu.lu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.