From: Jon Hunter <jonathanh@nvidia.com>
To: Radu Rendec <rrendec@redhat.com>, Thomas Gleixner <tglx@linutronix.de>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Daniel Tsai" <danielsftsai@google.com>,
"Marek Behún" <kabel@kernel.org>,
"Krishna Chaitanya Chundru" <quic_krichai@quicinc.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Brian Masney" <bmasney@redhat.com>,
"Eric Chanudet" <echanude@redhat.com>,
"Alessandro Carminati" <acarmina@redhat.com>,
"Jared Kangas" <jkangas@redhat.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] genirq: Update effective affinity for redirected interrupts
Date: Mon, 12 Jan 2026 21:32:13 +0000 [thread overview]
Message-ID: <bee812e6-85c6-4d82-8bfc-69517f17492d@nvidia.com> (raw)
In-Reply-To: <20260112211402.2927336-1-rrendec@redhat.com>
On 12/01/2026 21:14, Radu Rendec wrote:
> For redirected interrupts, irq_chip_redirect_set_affinity() does not
> update the effective affinity mask, which then triggers the warning in
> irq_validate_effective_affinity(). Also, because the effective affinity
> mask is empty, the cpumask_test_cpu(smp_processor_id(), m) condition in
> demux_redirect_remote() is always false, and the interrupt is always
> redirected, even if it's already running on the target CPU.
>
> Set the effective affinity mask to be the same as the requested affinity
> mask. It's worth noting that irq_do_set_affinity() filters out offline
> CPUs before calling chip->irq_set_affinity() (unless `force` is set), so
> the mask passed to irq_chip_redirect_set_affinity() is already filtered.
>
> The solution is not ideal because it may lie about the effective
> affinity of the demultiplexed ("child") interrupt. If the requested
> affinity mask includes multiple CPUs, the effective affinity, in
> reality, is the intersection between the requested mask and the
> demultiplexing ("parent") interrupt's effective affinity mask, plus
> the first CPU in the requested mask.
>
> Accurately describing the effective affinity of the demultiplexed
> interrupt is not trivial because it requires keeping track of the
> demultiplexing interrupt's effective affinity. That is tricky in the
> context of CPU hot(un)plugging, where interrupt migration ordering is
> not guaranteed. The solution in the initial version of the fixed patch,
> which stored the first CPU of the demultiplexing interrupt's effective
> affinity in the `target_cpu` field, has its own drawbacks and
> limitations.
>
> Fixes: fcc1d0dabdb6 ("genirq: Add interrupt redirection infrastructure")
> Reported-by: Jon Hunter <jonathanh@nvidia.com>
> Closes: https://lore.kernel.org/all/44509520-f29b-4b8a-8986-5eae3e022eb7@nvidia.com/
> Signed-off-by: Radu Rendec <rrendec@redhat.com>
> ---
> kernel/irq/chip.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index 433f1dd2b0ca7..35bc17bc369e0 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -1493,6 +1493,8 @@ int irq_chip_redirect_set_affinity(struct irq_data *data, const struct cpumask *
> struct irq_redirect *redir = &irq_data_to_desc(data)->redirect;
>
> WRITE_ONCE(redir->target_cpu, cpumask_first(dest));
> + irq_data_update_effective_affinity(data, dest);
> +
> return IRQ_SET_MASK_OK;
> }
> EXPORT_SYMBOL_GPL(irq_chip_redirect_set_affinity);
This is working for me ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-12 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 21:14 Radu Rendec
2026-01-12 21:32 ` Jon Hunter [this message]
2026-01-13 9:05 ` [tip: irq/msi] " tip-bot2 for Radu Rendec
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=bee812e6-85c6-4d82-8bfc-69517f17492d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=acarmina@redhat.com \
--cc=bhelgaas@google.com \
--cc=bmasney@redhat.com \
--cc=danielsftsai@google.com \
--cc=echanude@redhat.com \
--cc=jingoohan1@gmail.com \
--cc=jkangas@redhat.com \
--cc=kabel@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=robh@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®