linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: use irq_set_affinity with force=false when migrating irqs
Date: Mon, 1 Sep 2014 12:50:58 +0100	[thread overview]
Message-ID: <20140901115057.GH30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1409571966-18343-1-git-send-email-sudeep.holla@arm.com>

On Mon, Sep 01, 2014 at 12:46:06PM +0100, 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.
> 
> If irq_set_affinity is called 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 fixes the issue by calling irq_set_affinity with force=false
> so that cpu_online_mask is checked while setting the affinity in the
> cpu hotplug path.
> 
> Tested on TC2 hotpluging CPU0 in and out. Without this patch the system
> locks up as the IRQs are not migrated away from CPU0.
> 
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: <stable@vger.kernel.org> # 3.10.x
> ---
>  arch/arm/kernel/irq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Hi Russell,
> 
> If you or tglx has no objections to this patch, I will put it
> in your patch tracker.

Post discussion, I have no objections - except to the above comment.  Let
me rewrite it in a programming language, and maybe you can spot what's
wrong:

	if (russell_has_no_objection(patch) || tglx_has_no_objection(patch))
		submit_patch_to_tracker(patch);

Personally, I'd like to see tglx's ack on this first.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-09-01 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 11:46 [PATCH] arm: use irq_set_affinity with force=false when migrating irqs Sudeep Holla
2014-09-01 11:50 ` Russell King - ARM Linux [this message]
2014-09-01 12:18   ` Sudeep Holla
2014-09-01 12:56   ` Thomas Gleixner
2014-09-01 13:03     ` Sudeep Holla
2014-09-01 14:21 ` [PATCH v2] " Sudeep Holla
2014-09-01 15:50   ` Mark Rutland

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=20140901115057.GH30401@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).