[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bee812e6-85c6-4d82-8bfc-69517f17492d@nvidia.com>
Date: Mon, 12 Jan 2026 21:32:13 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Radu Rendec <rrendec@...hat.com>, Thomas Gleixner <tglx@...utronix.de>
Cc: Manivannan Sadhasivam <mani@...nel.org>,
Daniel Tsai <danielsftsai@...gle.com>, Marek Behún
<kabel@...nel.org>, Krishna Chaitanya Chundru <quic_krichai@...cinc.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Rob Herring <robh@...nel.org>,
Krzysztof Wilczyński <kwilczynski@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, Jingoo Han
<jingoohan1@...il.com>, Brian Masney <bmasney@...hat.com>,
Eric Chanudet <echanude@...hat.com>,
Alessandro Carminati <acarmina@...hat.com>, Jared Kangas
<jkangas@...hat.com>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH] genirq: Update effective affinity for redirected
interrupts
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@...dia.com>
> Closes: https://lore.kernel.org/all/44509520-f29b-4b8a-8986-5eae3e022eb7@nvidia.com/
> Signed-off-by: Radu Rendec <rrendec@...hat.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@...dia.com>
Thanks
Jon
--
nvpublic
Powered by blists - more mailing lists