[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150917160107.GO25634@arm.com>
Date: Thu, 17 Sep 2015 17:01:07 +0100
From: Will Deacon <will.deacon@....com>
To: Yang Yingliang <yangyingliang@...wei.com>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jiang Liu <jiang.liu@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Marc Zyngier <Marc.Zyngier@....com>,
Mark Rutland <Mark.Rutland@....com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>
Subject: Re: [RFC PATCH v4 3/4] arm64: fix a migrating irq bug when hotplug
cpu
On Thu, Sep 17, 2015 at 06:19:25AM +0100, Yang Yingliang wrote:
> When cpu is disabled, all irqs will be migratged to another cpu.
> In some cases, a new affinity is different, it needed to be coppied
> to irq's affinity. But if the type of irq is LPI, it's affinity will
> not be coppied because of irq_set_affinity's return value. Fix it by
> using irq_do_set_affinity.
>
> And migrating interrupts is a core code matter, so use the generic
> function move_irqs() to migrate interrupts in kernel/irq/migration.c.
>
> Cc: Jiang Liu <jiang.liu@...ux.intel.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Marc Zyngier <marc.zyngier@....com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Will Deacon <will.deacon@....com>
> Cc: Russell King - ARM Linux <linux@....linux.org.uk>
> Cc: Hanjun Guo <hanjun.guo@...aro.org>
> Signed-off-by: Yang Yingliang <yangyingliang@...wei.com>
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/irq.h | 1 -
> arch/arm64/kernel/irq.c | 62 --------------------------------------------
> arch/arm64/kernel/smp.c | 2 +-
> 4 files changed, 2 insertions(+), 64 deletions(-)
Removing code is always good, so:
Acked-by: Will Deacon <will.deacon@....com>
but obviously this depends on the core stuff.
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists