[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43F901BD926A4E43B106BF17856F075501A4A62498@orsmsx508.amr.corp.intel.com>
Date: Thu, 15 Dec 2011 10:38:20 -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
> We need a debug feature for this: CONFIG_DEBUG_BOOT_CPU_OFF=y or
> such (disabled by default): this feature would offline the boot
> CPU as soon as possible, and boot up userspace with the boot CPU
> offlined.
I would think the earliest time when CPU0 can be offline is right after do_initcalls() because do_initcalls() installs some cpu hotplug notifier.
But this will change generic code (e.g. add arch hook in init/main.c or add a new initcall level which is after level 7s).
Another way is to offline CPU0 (or any CPU) in /etc/rc.local. By this way, we don't change kernel. And this is safe, but a bit later than in kernel.
Any comment?
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