From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: use cpu_online_mask when using forced irq_set_affinity
Date: Fri, 23 May 2014 12:26:02 +0100 [thread overview]
Message-ID: <537F304A.1040909@arm.com> (raw)
In-Reply-To: <1399653640-21559-1-git-send-email-sudeep.holla@arm.com>
Hi Russell,
On 09/05/14 17:40, Sudeep Holla wrote:
> From: Sudeep Holla <sudeep.holla@arm.com>
>
> Commit 01f8fa4f01d8("genirq: Allow forcing cpu affinity of interrupts")
> enabled the forced irq_set_affinity which previously refused to route an
> interrupt to an offline cpu.
>
> Commit ffde1de64012("irqchip: Gic: Support forced affinity setting")
> implements this force logic and disables the cpu online check for GIC
> interrupt controller.
>
> When __cpu_disable calls migrate_irqs, it disables the current cpu in
> cpu_online_mask and uses forced irq_set_affinity to migrate the IRQs
> away from the cpu but passes affinity mask with the cpu being offlined
> also included in it.
>
> When calling irq_set_affinity with force == true in a cpu hotplug path,
> the caller must ensure that the cpu being offlined is not present in the
> affinity mask or it may be selected as the target CPU, leading to the
> interrupt not being migrated.
>
> This patch uses cpu_online_mask when using forced irq_set_affinity so
> that the IRQs are properly migrated away.
>
> Tested on TC2 hotpluging CPU0 in and out. Without this patch the system
> locks up as the IRQs are not migrated away from CPU0.
>
If you are fine with this change, can I put this in the patch tracker?
Regards,
Sudeep
> Cc: Russell King <linux@arm.linux.org.uk>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> arch/arm/kernel/irq.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/kernel/irq.c b/arch/arm/kernel/irq.c
> index 9723d17..1f216a5 100644
> --- a/arch/arm/kernel/irq.c
> +++ b/arch/arm/kernel/irq.c
> @@ -155,11 +155,15 @@ static bool migrate_one_irq(struct irq_desc *desc)
> if (irqd_is_per_cpu(d) || !cpumask_test_cpu(smp_processor_id(), affinity))
> return false;
>
> - if (cpumask_any_and(affinity, cpu_online_mask) >= nr_cpu_ids) {
> - affinity = cpu_online_mask;
> + if (cpumask_any_and(affinity, cpu_online_mask) >= nr_cpu_ids)
> ret = true;
> - }
>
> + /*
> + * when using forced irq_set_affinity we must ensure that the cpu
> + * being offlined is not present in the affinity mask, it may be
> + * selected as the target CPU otherwise
> + */
> + affinity = cpu_online_mask;
> c = irq_data_get_irq_chip(d);
> if (!c->irq_set_affinity)
> pr_debug("IRQ%u: unable to set affinity\n", d->irq);
>
next prev parent reply other threads:[~2014-05-23 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 16:40 [PATCH] arm: use cpu_online_mask when using forced irq_set_affinity Sudeep Holla
2014-05-23 11:26 ` Sudeep Holla [this message]
2014-05-23 12:10 ` Russell King - ARM Linux
2014-05-23 12:51 ` Sudeep Holla
2014-06-20 13:04 ` Sudeep Holla
2014-06-20 15:16 ` Russell King - ARM Linux
2014-07-17 9:58 ` Sudeep Holla
2014-08-25 9:55 ` Thomas Gleixner
2014-08-26 15:19 ` Sudeep Holla
2014-08-28 9:32 ` Thomas Gleixner
2014-08-28 10:12 ` Sudeep Holla
2014-08-28 10:16 ` Russell King - ARM Linux
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=537F304A.1040909@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).