All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Dawei Li <dawei.li@shingroup.cn>
Cc: tglx@linutronix.de, rafael@kernel.org, akpm@linux-foundation.org,
	maz@kernel.org, florian.fainelli@broadcom.com,
	chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
	anup@brainfault.org, palmer@dabbelt.com,
	samuel.holland@sifive.com, linux@rasmusvillemoes.dk,
	daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/7] irqchip/loongson-eiointc: Avoid explicit cpumask allocation on stack
Date: Tue, 16 Apr 2024 11:01:47 -0700	[thread overview]
Message-ID: <Zh69CzD26Z4hw6R9@yury-ThinkPad> (raw)
In-Reply-To: <20240416085454.3547175-5-dawei.li@shingroup.cn>

On Tue, Apr 16, 2024 at 04:54:51PM +0800, Dawei Li wrote:
> In general it's preferable to avoid placing cpumasks on the stack, as
> for large values of NR_CPUS these can consume significant amounts of
> stack space and make stack overflows more likely.
> 
> Use cpumask_first_and_and() to avoid the need for a temporary cpumask on
> the stack.
> 
> Signed-off-by: Dawei Li <dawei.li@shingroup.cn>
> ---
>  drivers/irqchip/irq-loongson-eiointc.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-loongson-eiointc.c b/drivers/irqchip/irq-loongson-eiointc.c
> index 4f5e6d21d77d..c7ddebf312ad 100644
> --- a/drivers/irqchip/irq-loongson-eiointc.c
> +++ b/drivers/irqchip/irq-loongson-eiointc.c
> @@ -93,19 +93,15 @@ static int eiointc_set_irq_affinity(struct irq_data *d, const struct cpumask *af
>  	unsigned int cpu;
>  	unsigned long flags;
>  	uint32_t vector, regaddr;
> -	struct cpumask intersect_affinity;
>  	struct eiointc_priv *priv = d->domain->host_data;
>  
>  	raw_spin_lock_irqsave(&affinity_lock, flags);
>  
> -	cpumask_and(&intersect_affinity, affinity, cpu_online_mask);
> -	cpumask_and(&intersect_affinity, &intersect_affinity, &priv->cpuspan_map);
> -
> -	if (cpumask_empty(&intersect_affinity)) {

This was unneeded because cpumask_and() returns true if there are set
bits.

For the series:

Reviewed-by: Yury Norov <yury.norov@gmail.com>

> +	cpu = cpumask_first_and_and(&priv->cpuspan_map, affinity, cpu_online_mask);
> +	if (cpu >= nr_cpu_ids) {
>  		raw_spin_unlock_irqrestore(&affinity_lock, flags);
>  		return -EINVAL;
>  	}
> -	cpu = cpumask_first(&intersect_affinity);
>  
>  	vector = d->hwirq;
>  	regaddr = EIOINTC_REG_ENABLE + ((vector >> 5) << 2);
> -- 
> 2.27.0

  reply	other threads:[~2024-04-16 18:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  8:54 [PATCH v2 0/7] Remove on-stack cpumask var for irq subsystem Dawei Li
2024-04-16  8:54 ` [PATCH v2 1/7] cpumask: introduce cpumask_first_and_and() Dawei Li
2024-04-16 17:45   ` Yury Norov
2024-04-16 17:49     ` Yury Norov
2024-04-17  1:35       ` Dawei Li
2024-04-24 20:04   ` [tip: irq/core] cpumask: Introduce cpumask_first_and_and() tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 2/7] irqchip/irq-bcm6345-l1: Avoid explicit cpumask allocation on stack Dawei Li
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 3/7] irqchip/gic-v3-its: " Dawei Li
2024-04-17 10:56   ` Marc Zyngier
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 4/7] irqchip/loongson-eiointc: " Dawei Li
2024-04-16 18:01   ` Yury Norov [this message]
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 5/7] irqchip/riscv-aplic-direct: " Dawei Li
2024-04-17 11:22   ` Anup Patel
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 6/7] irqchip/sifive-plic: " Dawei Li
2024-04-17 11:21   ` Anup Patel
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li
2024-04-16  8:54 ` [PATCH v2 7/7] cpuidle: " Dawei Li
2024-04-24 20:04   ` [tip: irq/core] " tip-bot2 for Dawei Li

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=Zh69CzD26Z4hw6R9@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=anup@brainfault.org \
    --cc=chenhuacai@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=dawei.li@shingroup.cn \
    --cc=florian.fainelli@broadcom.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=maz@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=rafael@kernel.org \
    --cc=samuel.holland@sifive.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.