From: "H. Peter Anvin" <hpa@zytor.com>
To: "Yu, Fenghua" <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
Arjan Dan De Ven <arjan@linux.intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"Srivatssa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Chen Gong <gong.chen@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>, x86 <x86@kernel.org>
Subject: RE: [PATCH v6 07/12] x86/head_32.S: Define start_cpu0
Date: Thu, 10 May 2012 18:53:08 -0500 [thread overview]
Message-ID: <554807c7-739e-4d5a-befc-34bf86399d75@email.android.com> (raw)
In-Reply-To: <3E5A0FA7E9CA944F9D5414FEC6C7122007715B10@ORSMSX105.amr.corp.intel.com>
I just meant: please check if there are any conflicts ..
"Yu, Fenghua" <fenghua.yu@intel.com> wrote:
>> -----Original Message-----
>> From: H. Peter Anvin [mailto:hpa@zytor.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.
next prev parent reply other threads:[~2012-05-10 23:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 16:16 [PATCH v6 0/12] x86: Arbitrary CPU hot(un)plug support Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 01/12] Documentations/cpu-hotplug.tx, kernel-parameters.txt: Add x86 CPU0 online/offline feature Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 02/12] x86/Kconfig: Add config switch for CPU0 hotplug Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 03/12] x86/topology.c: Support functions for CPU0 online/offline Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 04/12] x86/smpboot.c: Don't offline CPU0 if any irq can not be migrated out of it and remove CPU0 check in smp_callin() Fenghua Yu
2012-05-11 12:05 ` Thomas Gleixner
2012-05-11 18:42 ` Tony Luck
2012-05-14 12:17 ` Ingo Molnar
2012-05-14 16:40 ` Luck, Tony
2012-05-14 20:03 ` Yu, Fenghua
2012-05-17 22:47 ` Suresh Siddha
2012-05-18 1:47 ` Yu, Fenghua
2012-05-18 3:34 ` H. Peter Anvin
2012-05-17 22:52 ` H. Peter Anvin
2012-05-18 6:46 ` Ingo Molnar
2012-05-10 16:16 ` [PATCH v6 05/12] x86/power/cpu.c: Don't hibernate/suspend if CPU0 is offline Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 06/12] x86/head_64.S: Define start_cpu0 Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 07/12] x86/head_32.S: " Fenghua Yu
2012-05-10 17:31 ` H. Peter Anvin
2012-05-10 20:48 ` Yu, Fenghua
2012-05-10 23:53 ` H. Peter Anvin [this message]
2012-05-10 16:16 ` [PATCH v6 08/12] x86/smpboot.c: Wake up CPU0 via NMI instead of INITs Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 09/12] x86/common.c: Init CPU0 data during CPU0 online Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 10/12] x86/mtrr/main.c: Ask the first online CPU to save mtrr Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 11/12] x86/i387.c: Thread xstate is initialized only on CPU0 once Fenghua Yu
2012-05-10 16:16 ` [PATCH v6 12/12] x86/topology.c: debug CPU0 hotplug Fenghua Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=554807c7-739e-4d5a-befc-34bf86399d75@email.android.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=fenghua.yu@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®