linux-kernel - RE: [PATCH v6 07/12] x86/head_32.S: Define start

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: <554807c7-739e-4d5a-befc-34bf86399d75@email.android.com>
Date:	Thu, 10 May 2012 18:53:08 -0500
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Yu, Fenghua" <fenghua.yu@...el.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	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 v6 07/12] x86/head_32.S: Define start_cpu0

I just meant: please check if there are any conflicts .. 

"Yu, Fenghua" <fenghua.yu@...el.com> wrote:

>> -----Original Message-----
>> From: H. Peter Anvin [mailto:hpa@...or.com]
>> Sent: Thursday, May 10, 2012 10:31 AM
>> To: Yu, Fenghua; Ingo Molnar; Thomas Gleixner; Linus Torvalds; Andrew
>> Morton; Mallick, Asit K; Luck, Tony; Arjan Dan De Ven; Siddha, Suresh
>B;
>> Brown, Len; Srivatssa S. Bhat; Randy Dunlap; Chen Gong; linux-kernel;
>> linux-pm; x86
>> Subject: Re: [PATCH v6 07/12] x86/head_32.S: Define start_cpu0
>> 
>> Can you check how this interacts with tip:x86/realmode?
>
>When CPU0 is waken up by NMI, it's in protect mode and jumps to
>start_cpu0() which only sets up stack and goes to initial_code. CPU0
>wake up doesn't go through trampline and starts from real mode. This is
>different from waking up AP when AP goes through INIT/STARTUP sequence
>and starts from real mode.
>
>Thanks.
>
>-Fenghua

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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/