From: Bill Huang <bilhuang@nvidia.com>
To: "'Russell King - ARM Linux'" <linux@arm.linux.org.uk>
Cc: "'linux-tegra@vger.kernel.org'" <linux-tegra@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: Shutdown problem in SMP system happened on Tegra20
Date: Mon, 27 Aug 2012 13:43:07 +0800 [thread overview]
Message-ID: <A7051F87A141B744BCAF487D48E5B3BDF5BA98284F@HKMAIL02.nvidia.com> (raw)
In-Reply-To: <20120825071755.GG18957@n2100.arm.linux.org.uk>
> On Sat, Aug 25, 2012 at 08:00:56AM +0800, Bill Huang wrote:
> > nvpublic
> > > So what you're asking for is a feature to do what
> > > CONFIG_PM_SLEEP_SMP does, but without CONFIG_PM_SLEEP_SMP enabled?
> >
> > Yeah pretty much, I'm actually asking should we take care of this
> > since maybe not all platforms will have this config enabled?
> > >
> > > Why not just ensure that CONFIG_PM_SLEEP_SMP is enabled if your
> > > platform requires that the lowest CPU number be the CPU dealing with reboot?
> >
> > Someday we will have it enabled, but before that we'll hit the issue,
> > so you don't think this should be taken care of? Thanks.
>
> Well, just enable CONFIG_PM_SLEEP_SMP then - it'll be far better than trying to implement something in
> the ARM code, especially as sysrq can be used for poweroff/reboot etc (which will run from atomic
> contexts where you can't switch to another CPU.)
>
> What you're asking for will make these callbacks fragile for other platforms.
OK, thanks.
next prev parent reply other threads:[~2012-08-27 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 8:23 Bill Huang
2012-08-24 18:21 ` Russell King - ARM Linux
2012-08-25 0:00 ` Bill Huang
2012-08-25 7:17 ` Russell King - ARM Linux
2012-08-27 5:43 ` Bill Huang [this message]
2012-08-25 7:36 ` Shawn Guo
2012-08-25 7:52 ` Russell King - ARM Linux
2012-08-25 10:33 ` Shawn Guo
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=A7051F87A141B744BCAF487D48E5B3BDF5BA98284F@HKMAIL02.nvidia.com \
--to=bilhuang@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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®