From: Jon Hunter <jonathanh@nvidia.com>
To: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Radu Rendec <rrendec@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [tip: irq/msi] PCI: dwc: Enable MSI affinity support
Date: Tue, 6 Jan 2026 09:53:23 +0000 [thread overview]
Message-ID: <44509520-f29b-4b8a-8986-5eae3e022eb7@nvidia.com> (raw)
In-Reply-To: <176583448396.510.10427292538118156779.tip-bot2@tip-bot2>
Hi Radu,
On 15/12/2025 21:34, tip-bot2 for Radu Rendec wrote:
> The following commit has been merged into the irq/msi branch of tip:
>
> Commit-ID: eaf290c404f7c39f23292e9ce83b8b5b51ab598a
> Gitweb: https://git.kernel.org/tip/eaf290c404f7c39f23292e9ce83b8b5b51ab598a
> Author: Radu Rendec <rrendec@redhat.com>
> AuthorDate: Fri, 28 Nov 2025 16:20:55 -05:00
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitterDate: Mon, 15 Dec 2025 22:30:48 +01:00
>
> PCI: dwc: Enable MSI affinity support
>
> Leverage the interrupt redirection infrastructure to enable CPU affinity
> support for MSI interrupts. Since the parent interrupt affinity cannot
> be changed, affinity control for the child interrupt (MSI) is achieved
> by redirecting the handler to run in IRQ work context on the target CPU.
>
> This patch was originally prepared by Thomas Gleixner (see Link tag below)
> in a patch series that was never submitted as is, and only parts of that
> series have made it upstream so far.
>
> Originally-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Radu Rendec <rrendec@redhat.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Link: https://lore.kernel.org/linux-pci/878qpg4o4t.ffs@tglx/
> Link: https://patch.msgid.link/20251128212055.1409093-4-rrendec@redhat.com
With next-20260105 I am observing the following warning on the Tegra194
Jetson AGX platform ...
WARNING KERN genirq: irq_chip DW-PCI-MSI-0001:01:00.0 did not update
eff. affinity mask of irq 171
Bisect is point to this commit. This platform is using the driver
drivers/pci/controller/dwc/pcie-tegra194.c. Is there some default
affinity that we should be setting to avoid this warning?
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-06 9:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 21:20 [PATCH v3 0/3] Enable MSI affinity support for dwc PCI Radu Rendec
2025-11-28 21:20 ` [PATCH v3 1/3] genirq: Add interrupt redirection infrastructure Radu Rendec
2025-12-15 21:34 ` [tip: irq/msi] " tip-bot2 for Radu Rendec
2025-11-28 21:20 ` [PATCH v3 2/3] PCI: dwc: Code cleanup Radu Rendec
2025-12-15 21:34 ` [tip: irq/msi] " tip-bot2 for Radu Rendec
2025-11-28 21:20 ` [PATCH v3 3/3] PCI: dwc: Enable MSI affinity support Radu Rendec
2025-12-15 21:34 ` [tip: irq/msi] " tip-bot2 for Radu Rendec
2026-01-06 9:53 ` Jon Hunter [this message]
2026-01-06 15:07 ` Radu Rendec
2026-01-07 1:13 ` Radu Rendec
2026-01-20 18:01 ` [PATCH v3 3/3] " Jon Hunter
2026-01-20 22:30 ` Radu Rendec
2026-01-21 14:00 ` Jon Hunter
2026-01-22 23:31 ` Radu Rendec
2026-01-23 13:25 ` Jon Hunter
2026-01-26 7:59 ` Thomas Gleixner
2026-01-26 22:07 ` Jon Hunter
2026-01-26 22:26 ` Radu Rendec
2026-01-27 10:30 ` Thomas Gleixner
2026-01-27 13:34 ` Thomas Gleixner
2026-01-27 17:09 ` Jon Hunter
2026-01-27 21:30 ` [PATCH] genirq/redirect: Prevent writing MSI message on affinity change Thomas Gleixner
2026-01-29 22:51 ` [tip: irq/msi] " tip-bot2 for Thomas Gleixner
2026-03-26 3:48 ` [PATCH v3 3/3] PCI: dwc: Enable MSI affinity support Tsai Sung-Fu
2026-03-26 12:52 ` Thomas Gleixner
2026-05-22 20:27 ` Brian Norris
2026-05-23 0:07 ` Brian Norris
2026-05-25 16:48 ` Radu Rendec
2026-05-30 0:35 ` Brian Norris
2026-06-01 8:20 ` Niklas Cassel
2026-06-01 19:02 ` Brian Norris
2026-06-01 19:09 ` Brian Norris
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=44509520-f29b-4b8a-8986-5eae3e022eb7@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=rrendec@redhat.com \
--cc=tglx@linutronix.de \
--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®