All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: ak@muc.de, akpm <akpm@osdl.org>, zwane <zwane@arm.linux.org.uk>,
	rusty@rustycorp.com.au, vatsa@in.ibm.com,
	lkml <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org
Subject: Re: [patch 0/4] CPU Hotplug support for X86_64
Date: Tue, 24 May 2005 17:31:38 +0800	[thread overview]
Message-ID: <1116927099.3827.2.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <20050524081113.409604000@csdlinux-2.jf.intel.com>

On Tue, 2005-05-24 at 01:11 -0700, Ashok Raj wrote:
> TBD: 
> 
> 1. Track down CONFIG_SCHED_SMT Oops with both cpu up/down.
> 2. Test on real NUMA hw. 
> 
With below patch, cpu hotplug works with SCHED_SMT enabled in my test.
set_cpu_sibling_map is invoked before cpu is set to online.

Thanks,
Shaohua

--- a/arch/x86_64/kernel/smpboot.c.orig	2005-05-24 16:47:57.000000000 +0800
+++ b/arch/x86_64/kernel/smpboot.c	2005-05-24 16:48:31.000000000 +0800
@@ -443,7 +443,7 @@ set_cpu_sibling_map(int cpu)
 	int i;
 
 	if (smp_num_siblings > 1) {
-		for_each_online_cpu(i) {
+		for (i = 0; i < NR_CPUS; i++) {
 			if (cpu_core_id[cpu] == cpu_core_id[i]) {
 				cpu_set(i, cpu_sibling_map[cpu]);
 				cpu_set(cpu, cpu_sibling_map[i]);
@@ -454,7 +454,7 @@ set_cpu_sibling_map(int cpu)
 	}
 
 	if (current_cpu_data.x86_num_cores > 1) {
-		for_each_online_cpu(i) {
+		for (i = 0; i < NR_CPUS; i++) {
 			if (phys_proc_id[cpu] == phys_proc_id[i]) {
 				cpu_set(i, cpu_core_map[cpu]);
 				cpu_set(cpu, cpu_core_map[i]);



  parent reply	other threads:[~2005-05-24 10:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24  8:11 [patch 0/4] CPU Hotplug support for X86_64 Ashok Raj
2005-05-24  8:11 ` [patch 1/4] " Ashok Raj
2005-05-24 12:15   ` Andi Kleen
2005-05-24 15:51     ` Ashok Raj
2005-05-24 18:18       ` Andi Kleen
2005-05-24  8:11 ` [patch 2/4] " Ashok Raj
2005-05-24 12:24   ` Andi Kleen
2005-05-24  8:11 ` [patch 3/4] " Ashok Raj
2005-05-24 12:27   ` Andi Kleen
2005-05-24  8:11 ` [patch 4/4] " Ashok Raj
2005-05-24 12:28   ` Andi Kleen
2005-05-24  9:31 ` Shaohua Li [this message]
2005-05-25 22:16   ` [patch 0/4] " Matthew Dobson
2005-05-26  0:11     ` Ashok Raj
  -- strict thread matches above, loose matches on Subject: below --
2005-05-24  7:27 Ashok Raj

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=1116927099.3827.2.camel@linux-hp.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustycorp.com.au \
    --cc=vatsa@in.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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.