linux-kernel - Re: [PATCH v4 0/7] x86: BSP or CPU0 online/offline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4EDDE5D0.7030906@linux.vnet.ibm.com>
Date:	Tue, 06 Dec 2011 15:22:16 +0530
From:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Fenghua Yu <fenghua.yu@...el.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Thomas Gleixner <tglx@...utronix.de>,
	H Peter Anvin <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Tony Luck <tony.luck@...el.com>,
	Arjan van de Ven <arjan.van.de.ven@...el.com>,
	Suresh B Siddha <suresh.b.siddha@...el.com>,
	Len Brown <len.brown@...el.com>,
	Randy Dunlap <rdunlap@...otime.net>,
	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>,
	Tejun Heo <tj@...nel.org>, Borislav Petkov <bp@...64.org>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>
Subject: Re: [PATCH v4 0/7] x86: BSP or CPU0 online/offline

On 12/06/2011 02:28 PM, Ingo Molnar wrote:

> 
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
>> Secondly, and more importantly, is there *any* hardware in 
>> existence that has a BIOS that can suspend/resume successfully 
>> with BSP offlined? If such hardware exists then we need to 
>> support it properly - initially perhaps by whitelisting such 
>> systems.
> 
> I suspect the answer to that is 'no' - as resume is really just 
> a fresh bootup of the physical CPU and BIOSen just start on the 
> boot CPU, no questions asked.
> 
> So the right approach there would be to detect the case where we 
> boot up back from S2RAM resume on an offlined CPU (the BSP is 
> really just one of the possibilities - in theory a S2RAM resume 
> could boot back up on any of the APs as well) - the resume code 
> should move off that CPU ASAP and keep that CPU offlined.
> 
> But the hibernation angle should be considered. Hibernation 
> already has to deal with the case where someone physically 
> unplugs a CPU and then resumes from the disk image, right? How 
> does the hibernation code handle that case currently?
> 


Oh, wait a minute. Are we talking about physical CPU Hotplug in between
hibernation and restore? AFAIK, currently we don't handle that at all. 
One of the things I recall in this context is that, while developing
the x86 microcode update optimization patch (now, mainline commit Id
7098944), it was pointed out that physical CPU hotplug on x86, and that
too *in-between* hibernation and restore, is very far-fetched and not
handled at present.

I had posted another patch to go along with the above optimization patch
so that we don't break stuff when physical cpu hotplug comes into picture.
Link: http://thread.gmane.org/gmane.linux.kernel/1205405/focus=1205784
May be it will come of use now, as it is, or in a better form.

Regards,
Srivatsa S. Bhat
IBM Linux Technology Center

--
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/