[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v8l4kfpr.ffs@tglx>
Date: Tue, 17 Jan 2023 22:34:40 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Johan Hovold <johan+linaro@...nel.org>,
Marc Zyngier <maz@...nel.org>
Cc: x86@...nel.org, platform-driver-x86@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org,
Johan Hovold <johan+linaro@...nel.org>,
Hsin-Yi Wang <hsinyi@...omium.org>,
Mark-PK Tsai <mark-pk.tsai@...iatek.com>
Subject: Re: [PATCH v4 08/19] irqdomain: Refactor __irq_domain_alloc_irqs()
On Mon, Jan 16 2023 at 14:50, Johan Hovold wrote:
> Refactor __irq_domain_alloc_irqs() so that it can be called internally
> while holding the irq_domain_mutex.
>
> This will be used to fix a shared-interrupt mapping race.
No functional change. The split out internal function will be used to
fix a shared interrupt mapping race. This change is therefore tagged
with the same fixes tag.
Fixes: ....
> -int __irq_domain_alloc_irqs(struct irq_domain *domain, int irq_base,
> - unsigned int nr_irqs, int node, void *arg,
> - bool realloc, const struct irq_affinity_desc *affinity)
> +static int ___irq_domain_alloc_irqs(struct irq_domain *domain, int irq_base,
> + unsigned int nr_irqs, int node, void *arg,
> + bool realloc, const struct irq_affinity_desc *affinity)
__ vs. ___ is almost undistinguishable.
irq_domain_alloc_irqs_locked() nicely explains what this is about, no?
Thanks,
tglx
Powered by blists - more mailing lists