From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Luigi Rizzo <lrizzo@google.com>
Subject: [patch V2 0/3] x86/irq: Bugfix and cleanup for posted MSI interrupts
Date: Tue, 25 Nov 2025 22:50:43 +0100 (CET) [thread overview]
Message-ID: <20251125214446.766096680@linutronix.de> (raw)
A small update to V1 which can be found here:
https://lore.kernel.org/lkml/20251125101912.564125647@linutronix.de
Luigi reported that the retrigger mechanism for posted MSI interrupts is
broken. That happens because retrigger sends an IPI to the actual allocated
vector, which is handled correctly, but lacks an EOI. That leaves a stale
APIC ISR bit around.
The following series addresses this and does some related cleanups in that
area on top.
Changes vs. V1:
Use __this_cpu_*() - Luigi
Thanks,
tglx
---
arch/x86/include/asm/irq_remapping.h | 12 ++++++-
arch/x86/kernel/irq.c | 54 +++++++++++++++++++++++------------
drivers/iommu/intel/irq_remapping.c | 12 +++----
3 files changed, 52 insertions(+), 26 deletions(-)
next reply other threads:[~2025-11-25 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:50 Thomas Gleixner [this message]
2025-11-25 21:50 ` [patch V2 1/3] x86/msi: Make irq_retrigger() functional for posted MSI Thomas Gleixner
2025-12-17 17:48 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2025-11-25 21:50 ` [patch V2 2/3] x86/irq: Cleanup posted MSI code Thomas Gleixner
2025-12-17 17:48 ` [tip: x86/irq] " tip-bot2 for Thomas Gleixner
2025-12-18 22:03 ` tip-bot2 for Thomas Gleixner
2025-11-25 21:50 ` [patch V2 3/3] x86/irq_remapping: Sanitize posted_msi_supported() Thomas Gleixner
2025-12-17 17:48 ` [tip: x86/irq] " tip-bot2 for Thomas Gleixner
2025-12-18 22:03 ` tip-bot2 for Thomas Gleixner
2025-12-17 17:03 ` [patch V2 0/3] x86/irq: Bugfix and cleanup for posted MSI interrupts Luigi Rizzo
2025-12-17 17:37 ` 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=20251125214446.766096680@linutronix.de \
--to=tglx@linutronix.de \
--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.