From: Ashok Raj <ashok.raj@intel.com>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
Ashok Raj <ashok.raj@intel.com>, 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: Wed, 25 May 2005 17:11:55 -0700 [thread overview]
Message-ID: <20050525171154.A10018@unix-os.sc.intel.com> (raw)
In-Reply-To: <4294F948.20004@us.ibm.com>; from colpatch@us.ibm.com on Wed, May 25, 2005 at 03:16:40PM -0700
On Wed, May 25, 2005 at 03:16:40PM -0700, Matthew Dobson wrote:
> Shaohua Li wrote:
> > On Tue, 2005-05-24 at 01:11 -0700, Ashok Raj wrote:
> >
> > 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
>
> I'm not sure, but you probably want "for_each_cpu(i)" instead of "for (i =
> 0; i < NR_CPUS; i++)" below.
>
I have a new set of patches just getting ready with final comments from Andi
This version already uses for_each_cpu varient.
Cheers,
ashok
next prev parent reply other threads:[~2005-05-26 0:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 8:11 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 ` [patch 0/4] " Shaohua Li
2005-05-25 22:16 ` Matthew Dobson
2005-05-26 0:11 ` Ashok Raj [this message]
-- 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=20050525171154.A10018@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustycorp.com.au \
--cc=shaohua.li@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome