From: Shay Drori <shayd@nvidia.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: pci_msix_alloc_irq_at() affinity
Date: Mon, 5 Aug 2024 08:34:47 +0300 [thread overview]
Message-ID: <16fbd3eb-92e2-4e6f-b020-4f5a2feee4ad@nvidia.com> (raw)
In-Reply-To: <87ttgcuuvi.ffs@tglx>
On 26/07/2024 16:48, Thomas Gleixner wrote:
> External email: Use caution opening links or attachments
>
>
> On Thu, Jul 25 2024 at 08:34, Shay Drori wrote:
>> I did some testing with pci_msix_alloc_irq_at() and I noticed that the
>> affinity provided, via “struct irq_affinity_desc *af_desc”, doesn’t have
>> any affect.
>>
>> After some digging, I found out that irq_setup_affinity(), which is
>> called by request_irq(), is setting the affinity as all the CPUs online,
>> ignoring the affinity provided in pci_msix_alloc_irq_at().
>> Is this on purpose or a bug?
>
> It's an oversight. So far this has only been used with managed
> interrupts and the non-managed parts at the beginning or end of the
> interrupt group have been assigned the default affinity which makes this
> obviously a non-problem because the startup code uses the default
> affinity too.
>
>> P.S. The bellow diff honors the affinity provided in
>> pci_msix_alloc_irq_at()
>>
>> --- a/kernel/irq/irqdesc.c
>> +++ b/kernel/irq/irqdesc.c
>> @@ -530,6 +530,7 @@ static int alloc_descs(unsigned int start, unsigned
>> int cnt, int node,
>> flags = IRQD_AFFINITY_MANAGED |
>> IRQD_MANAGED_SHUTDOWN;
>> }
>> + flags |= IRQD_AFFINITY_SET;
>> mask = &affinity->mask;
>> node = cpu_to_node(cpumask_first(mask));
>> affinity++;
>
> Looks about right, though the diff is whitespace damaged.
>
> Care to submit a proper patch?
sorry for the late reply, Yes.
on-top of which kernel branch to create the patch?
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2024-08-05 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 5:34 pci_msix_alloc_irq_at() affinity Shay Drori
2024-07-26 13:48 ` Thomas Gleixner
2024-08-05 5:34 ` Shay Drori [this message]
2024-08-05 8:38 ` Thomas Gleixner
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=16fbd3eb-92e2-4e6f-b020-4f5a2feee4ad@nvidia.com \
--to=shayd@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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