mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: WeitaoWang-oc <weitaowang-oc@zhaoxin.com>
To: Koichiro Den <den@valinux.co.jp>
Cc: tglx@linutronix.de, 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: Wed, 30 Sep 2026 15:33:47 +0800	[thread overview]
Message-ID: <345d4bc2-1c50-4f10-ba5c-ca49e4843507@zhaoxin.com> (raw)
In-Reply-To: <6mg2eqdehsmb5fh6hf7icsha2547xfdfvulnycawiit2czhhmh@6bbmicaoz2zd>

On 9/30/26 00: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.
> 
> Hi Weitao, thanks for catching this.
> 
>>
>> 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")
> 
> 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. This
> left the race unfixed and also made maskable interrupts possibly take the slow
> path unnecessarily. Sorry for the trouble. Feel free to use this if it helps:
> 
>    Reviewed-by: Koichiro Den <den@valinux.co.jp>
> 
> Best regards,
> Koichiro

Hi Koichiro,

Thank you four suggestion and review. I'll send a v2 patch.

Best Regards,
Weitao

  reply	other threads:[~2026-09-30  7:35 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 [this message]
2026-10-15 22:12   ` Thomas Gleixner
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=345d4bc2-1c50-4f10-ba5c-ca49e4843507@zhaoxin.com \
    --to=weitaowang-oc@zhaoxin.com \
    --cc=CobeChen@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=tglx@linutronix.de \
    --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®