[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43F901BD926A4E43B106BF17856F075501A23A3010@orsmsx508.amr.corp.intel.com>
Date: Thu, 8 Dec 2011 16:41:30 -0800
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Thomas Gleixner <tglx@...utronix.de>,
H Peter Anvin <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Luck, Tony" <tony.luck@...el.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@...el.com>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
"Brown, Len" <len.brown@...el.com>,
Randy Dunlap <rdunlap@...otime.net>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-pm <linux-pm@...r.kernel.org>, x86 <x86@...nel.org>
Subject: RE: [PATCH v4 0/7] x86: BSP or CPU0 online/offline
>
> * Fenghua Yu <fenghua.yu@...el.com> wrote:
> Then if demand for this picks up some more intelligent method of
> cooperating with the firmware could be added: the firmware could
> actually signal to us whether it supports suspend/resume from
> other than the boot CPU.
We started to think how to handle the resume issue in firmware,
e.g. the way you talked, or change boot CPU to another online CPU
to execute resume procedure.
A firmware solution is a long run. Currently we don't suspend/hibernate
when BSP is offline. If a firmware solution is available, we can
change the sanity check to allow suspend/hibernate if CPU0 is offline
for new firmware. But even when the solution is available in new
firmware, we still need to do the same sanity check on legacy firmware.
Thanks.
-Fenghua
--
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