From: Catalin Marinas <catalin.marinas@arm.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: [RFC PATCH v6 2/3] arm64: fix a migrating irq bug when hotplug cpu
Date: Fri, 9 Oct 2015 17:55:01 +0100 [thread overview]
Message-ID: <20151009165501.GY17192@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1443087135-17044-3-git-send-email-yangyingliang@huawei.com>
On Thu, Sep 24, 2015 at 05:32:14PM +0800, Yang Yingliang wrote:
> When cpu is disabled, all irqs will be migratged to another cpu.
> In some cases, a new affinity is different, the old affinity need
> to be updated and if irq_set_affinity's return value is IRQ_SET_MASK_OK_DONE,
> the old affinity can not be updated. Fix it by using irq_do_set_affinity.
>
> And migrating interrupts is a core code matter, so use the generic
> function irq_migrate_all_off_this_cpu() to migrate interrupts in
> kernel/irq/migration.c.
>
> Cc: Jiang Liu <jiang.liu@linux.intel.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>
> Cc: Hanjun Guo <hanjun.guo@linaro.org>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
I queued this patch for 4.4, on top of this branch from Thomas:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-arm
The arm (32-bit) patch would need to go via Russell's tree (patch
system, pull request or waiting until 4.4-rc1, it's up to Russell).
Thanks.
--
Catalin
next prev parent reply other threads:[~2015-10-09 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 9:32 [RFC PATCH v6 0/3] arm/arm64: " Yang Yingliang
2015-09-24 9:32 ` [RFC PATCH v6 1/3] genirq: introduce CONFIG_GENERIC_IRQ_MIGRATION and kernel/irq/cpuhotplug.c Yang Yingliang
2015-10-01 14:18 ` [tip:irq/core] genirq: Introduce generic irq migration for cpu hotunplug tip-bot for Yang Yingliang
2015-10-01 14:24 ` Thomas Gleixner
2015-10-01 14:47 ` Catalin Marinas
2015-09-24 9:32 ` [RFC PATCH v6 2/3] arm64: fix a migrating irq bug when hotplug cpu Yang Yingliang
2015-10-09 16:55 ` Catalin Marinas [this message]
2015-09-24 9:32 ` [RFC PATCH v6 3/3] arm: " Yang Yingliang
2015-10-13 19:28 ` Russell King - ARM Linux
2015-10-21 11:47 ` Geert Uytterhoeven
2015-10-21 20:29 ` Russell King - ARM Linux
2015-10-22 9:26 ` Russell King - ARM Linux
2015-10-22 9:46 ` Geert Uytterhoeven
2015-10-22 10:56 ` Yang Yingliang
2015-10-22 11:13 ` Russell King - ARM Linux
2015-10-22 12:43 ` Thomas Gleixner
2015-10-22 16:34 ` Catalin Marinas
2015-12-15 6:59 ` Yang Yingliang
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=20151009165501.GY17192@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=yangyingliang@huawei.com \
/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
all inboxes | Powered by JetHome®