[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C7122007789378@ORSMSX105.amr.corp.intel.com>
Date: Fri, 24 Aug 2012 19:53:31 +0000
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
H Peter Anvin <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Mallick, Asit K" <asit.k.mallick@...el.com>,
"Luck, Tony" <tony.luck@...el.com>,
Arjan Dan De Ven <arjan@...ux.intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
"Brown, Len" <len.brown@...el.com>,
"Srivatssa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
Randy Dunlap <rdunlap@...otime.net>,
Chen Gong <gong.chen@...ux.intel.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-pm <linux-pm@...r.kernel.org>, x86 <x86@...nel.org>
Subject: RE: [PATCH v7 02/12] x86/Kconfig: Add config switch for CPU0 hotplug
> And, btw, maybe I didn't catch this earlier, but why is in all
> user-visible options the thing called "cpu0_*"? Wouldn't it be better
> to
> call it "bsp_*"?
The kernel parameter was called bsp_hotplug before. It was changed to cpu0_hotplug in v5 to keep uniform cpu0/CPU0 names.
Thanks.
-Fenghua
Powered by blists - more mailing lists