linux-kernel - Re: [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP

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 for Android: free password hash cracker in your pocket

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

Message-ID: <513D5962.7000209@zytor.com>
Date:	Sun, 10 Mar 2013 21:11:14 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	HATAYAMA Daisuke <d.hatayama@...fujitsu.com>
CC:	ebiederm@...ssion.com, len.brown@...el.com, fenghua.yu@...el.com,
	x86@...nel.org, kexec@...ts.infradead.org,
	linux-kernel@...r.kernel.org, rob.herring@...xeda.com,
	grant.likely@...retlab.ca, tglx@...utronix.de, mingo@...e.hu,
	vgoyal@...hat.com
Subject: Re: [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP

On 03/10/2013 07:13 PM, HATAYAMA Daisuke wrote:
> 
> It seems to me that at least there needs to be the following design
> policy for multiple CPUs on the 2nd kenrel:
> 
> - There's no firmware, kernel components and modules that depend on
>   BSP flag being kept set on the original BSP flag and never set BSP
>   flag of any of the existing CPUs again at runtime.
> 

And that is provably false in the case of firmware.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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