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: <20111206103500.GD15966@elte.hu>
Date:	Tue, 6 Dec 2011 11:35:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
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


* Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com> wrote:

> > 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. [...]

Well, not hotplug, but plain old-fashioned: 'hibernate the box, 
take out a CPU physically and thaw' kind of hardware change.

How will the hibernation code handle this case?

Thanks,

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