All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: not set boot cpu in cpu_online_map at smp_prepare_boot_cpu
Date: Mon, 26 Nov 2007 14:06:43 -0800	[thread overview]
Message-ID: <474B4373.9060802@sun.com> (raw)
In-Reply-To: <1196110666.6352.309.camel@bodhitayantram.eng.vmware.com>

Zachary Amsden wrote:
> On Mon, 2007-11-26 at 00:38 -0800, Yinghai Lu wrote:
>> [PATCH] x86_64: not set boot cpu in cpu_online_map at smp_prepare_boot_cpu
>>
>> in init/main.c boot_cpu_init() does that before
>>
>> Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>
>>
>> diff --git a/arch/x86/kernel/smpboot_64.c b/arch/x86/kernel/smpboot_64.c
>> index 500670c..966d124 100644
>> --- a/arch/x86/kernel/smpboot_64.c
>> +++ b/arch/x86/kernel/smpboot_64.c
>> @@ -912,7 +912,7 @@ void __init smp_prepare_cpus(unsigned int max_cpus)
>>  void __init smp_prepare_boot_cpu(void)
>>  {
>>  	int me = smp_processor_id();
>> -	cpu_set(me, cpu_online_map);
>> +	/* already set me in cpu_online_map in boot_cpu_init() */
>>  	cpu_set(me, cpu_callout_map);
>>  	per_cpu(cpu_state, me) = CPU_ONLINE;
>>  }
> 
> 
> This ordering can be tricky wrt CPU hotplug.  Are you sure you are not
> breaking CPU hotplug?  AFAIK, x86_64 has that right and the 32-bit code
> had it wrong.


CPU hot plug path will call smp_prepare_boot_cpu?
it is using __init instead of __cpuinit?

YH

  reply	other threads:[~2007-11-26 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26  8:38 [PATCH] x86_64: not set boot cpu in cpu_online_map at smp_prepare_boot_cpu Yinghai Lu
2007-11-26 20:57 ` Zachary Amsden
2007-11-26 22:06   ` Yinghai Lu [this message]
2007-11-26 22:36     ` Zachary Amsden
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28  2:28 Yinghai Lu
2008-01-28 12:40 ` Ingo Molnar

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=474B4373.9060802@sun.com \
    --to=yinghai.lu@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zach@vmware.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.