From: Thomas Gleixner <tglx@linutronix.de>
To: Koichiro Den <den@valinux.co.jp>,
WeitaoWang-oc <WeitaoWang-oc@zhaoxin.com>
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
WeitaoWang@zhaoxin.com, wwt8723@163.com, CobeChen@zhaoxin.com,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/apic/msi: Fix MSI interrupt affinity configuration
Date: Fri, 16 Oct 2026 00:12:41 +0200 [thread overview]
Message-ID: <87jynid352.ffs@fw13> (raw)
In-Reply-To: <6mg2eqdehsmb5fh6hf7icsha2547xfdfvulnycawiit2czhhmh@6bbmicaoz2zd>
On Wed, Sep 30 2026 at 01:29, Koichiro Den wrote:
> On Tue, Sep 29, 2026 at 12:48:39AM +0800, WeitaoWang-oc wrote:
>> commit b56ebe7c896d ("x86/apic/msi: Fix misconfigured non-maskable MSI
>> quirk") try to fix the issue of misconfigured non-maskable MSI quirk.
>> For non-maskable MSI interrupts, use the slow path to fix the MSI affinity
>> race. Maskable MSI interrupts use the direct path to update configuration
>> info. However, the current code logic is the opposite as only maskable
>> MSI interrupts will enable reservation mode.
Please read:
https://docs.kernel.org/process/maintainer-tip.html#changelog
and restructure and reword the changelog accordingly. The above is
incomprehensible word salad.
>> Fixes: ef8dd01538ea ("genirq/msi: Make interrupt allocation less convoluted")
>
> I'd rather (or also) add:
>
> Fixes: b56ebe7c896d ("x86/apic/msi: Fix misconfigured non-maskable MSI quirk")
That's the correct Fixes tag.
> As I recall, I started out trying to fix the issue, but then got too focused on
> removing the flag. I missed that the check needed to be inverted.
I missed it too :)
>> @@ -62,7 +62,7 @@ msi_set_affinity(struct irq_data *irqd, const struct cpumask *mask, bool force)
>> * - The interrupt is not yet started up
>> * - The new destination CPU is the same as the old destination CPU
>> */
>> - if (!irqd_can_reserve(irqd) ||
>> + if (irqd_can_reserve(irqd) ||
Amazing that this went unnoticed so long ...
>> cfg->vector == old_cfg.vector ||
>> old_cfg.vector == MANAGED_IRQ_SHUTDOWN_VECTOR ||
>> !irqd_is_started(irqd) ||
>> --
>> 2.32.0
>>
next prev parent reply other threads:[~2026-10-15 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:48 WeitaoWang-oc
2026-09-29 16:29 ` Koichiro Den
2026-09-30 7:33 ` WeitaoWang-oc
2026-10-15 22:12 ` Thomas Gleixner [this message]
2026-10-16 3:36 ` [此为外部邮件 谨防风险] " WeitaoWang-oc
2026-10-16 9:30 ` Thomas Gleixner
2026-10-16 11:58 ` [PATCH v3] " WeitaoWang-oc
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=87jynid352.ffs@fw13 \
--to=tglx@linutronix.de \
--cc=CobeChen@zhaoxin.com \
--cc=WeitaoWang-oc@zhaoxin.com \
--cc=WeitaoWang@zhaoxin.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=den@valinux.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wwt8723@163.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 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®