From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linuxppc-dev@lists.ozlabs.org list"
<linuxppc-dev@lists.ozlabs.org>,
Zhao Chenhui <chenhui.zhao@freescale.com>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc/smp: Do not disable IPI interrupts during suspend
Date: Sat, 28 Jul 2012 09:03:00 -0500 [thread overview]
Message-ID: <31CC815F-472E-4211-85E5-3DB644105AF4@kernel.crashing.org> (raw)
In-Reply-To: <1343427631.21647.1.camel@pasglop>
On Jul 27, 2012, at 5:20 PM, Benjamin Herrenschmidt wrote:
> On Fri, 2012-07-27 at 16:58 -0500, Kumar Gala wrote:
>> On Jul 20, 2012, at 7:47 AM, Zhao Chenhui wrote:
>>=20
>>> During suspend, all interrupts including IPI will be disabled. In =
this case,
>>> the suspend process will hang in SMP. To prevent this, pass the flag
>>> IRQF_NO_SUSPEND when requesting IPI irq.
>>>=20
>>> Signed-off-by: Zhao Chenhui <chenhui.zhao@freescale.com>
>>> Signed-off-by: Li Yang <leoli@freescale.com>
>>> ---
>>> arch/powerpc/kernel/smp.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>=20
>> BenH,
>>=20
>> Can you ack?
>=20
> No I'll merge it but not until it's been in next for a bit unless you
> have some strong emergency there, it's on my mental list of things to
> shovel into next after rc1.
I wasn't clear, I was meaning for my 'next' tree, not 3.6. Trying to =
get these FSL PM patches into my 'next' for 3.7.
- k
> Curiosity: didn't we use to disable all non-boot CPUs on suspend ?
>=20
> Cheers,
> Ben.
>=20
>> - k
>>=20
>>>=20
>>> diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
>>> index fecb038..d26bbf8 100644
>>> --- a/arch/powerpc/kernel/smp.c
>>> +++ b/arch/powerpc/kernel/smp.c
>>> @@ -171,7 +171,7 @@ int smp_request_message_ipi(int virq, int msg)
>>> }
>>> #endif
>>> err =3D request_irq(virq, smp_ipi_action[msg],
>>> - IRQF_PERCPU | IRQF_NO_THREAD,
>>> + IRQF_PERCPU | IRQF_NO_THREAD | =
IRQF_NO_SUSPEND,
>>> smp_ipi_name[msg], 0);
>>> WARN(err < 0, "unable to request_irq %d for %s (rc %d)\n",
>>> virq, smp_ipi_name[msg], err);
>>> --=20
>>> 1.6.4.1
>>>=20
>=20
next prev parent reply other threads:[~2012-07-28 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 12:47 [PATCH] powerpc/smp: Do not disable IPI interrupts during suspend Zhao Chenhui
2012-07-27 21:58 ` Kumar Gala
2012-07-27 22:20 ` Benjamin Herrenschmidt
2012-07-28 14:03 ` Kumar Gala [this message]
2012-08-02 10:04 ` Zhao Chenhui
2012-08-10 12:40 ` Kumar Gala
2012-09-13 18:16 ` Kumar Gala
2012-09-13 22:11 ` Benjamin Herrenschmidt
2012-09-19 14:52 ` Kumar Gala
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=31CC815F-472E-4211-85E5-3DB644105AF4@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=chenhui.zhao@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).