From: linas@austin•ibm.com (Linas Vepstas)
To: Michael Ellerman <michael@ellerman•id.au>
Cc: srinivasa@in•ibm.com, ego@in•ibm.com, linuxppc-dev@ozlabs•org,
Paul Mackerras <paulus@samba•org>,
Anton Blanchard <anton@samba•org>,
ntl@pobox•com
Subject: Re: [PATCH] Reorganise and then fixup the pseries cpu hotplug code
Date: Mon, 27 Nov 2006 15:10:13 -0600 [thread overview]
Message-ID: <20061127211013.GI10879@austin.ibm.com> (raw)
In-Reply-To: <20061123021132.B03F767C18@ozlabs.org>
On Thu, Nov 23, 2006 at 01:11:30PM +1100, Michael Ellerman wrote:
> The pseries cpu hotplug code is currently spread between ./kernel/rtas.c,
> ./platforms/pseries/smp.c and ./platforms/pseries/setup.c. Some of it is
> not #ifdef CONFIG_HOTPLUG_CPU, but it should be.
>
> Signed-off-by: Michael Ellerman <michael@ellerman•id.au>
Ack'ed by: Linas Vepstas <linas@austin•ibm.com>
> Linas, Srinivasa, can you test that this addresses the problems you
> were seeing. It should, but it'd be good if you could test it.
Actually, I was debugging Srinivasa's problem long-distance, which
was an internally-reported bugzilla bug that had landed in my lap.
I don't actually have a testable config. But, based on this chain
of mails, I am happy with the result!
--linas
next prev parent reply other threads:[~2006-11-27 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 2:11 [PATCH] Reorganise and then fixup the pseries cpu hotplug code Michael Ellerman
2006-11-24 11:03 ` Srinivasa Ds
2006-11-27 8:13 ` Srinivasa Ds
2006-11-27 21:10 ` Linas Vepstas [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 15:40 [RFC] [PATCH] cpu hotplug on power based systems Nathan Lynch
2006-11-17 3:36 ` [PATCH] Reorganise and then fixup the pseries cpu hotplug code Michael Ellerman
2006-11-17 3:59 ` Michael Ellerman
2006-11-17 4:31 ` Stephen Rothwell
2006-11-17 4:44 ` Michael Ellerman
2006-11-17 5:02 ` Stephen Rothwell
2006-11-17 18:11 ` Linas Vepstas
2006-11-20 0:44 ` Michael Ellerman
2006-11-17 18:04 ` Linas Vepstas
2006-11-20 1:08 ` Michael Ellerman
2006-11-20 4:22 ` jschopp
2006-11-20 5:59 ` Michael Ellerman
2006-11-21 16:43 ` Nathan Lynch
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=20061127211013.GI10879@austin.ibm.com \
--to=linas@austin$(echo .)ibm.com \
--cc=anton@samba$(echo .)org \
--cc=ego@in$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=michael@ellerman$(echo .)id.au \
--cc=ntl@pobox$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=srinivasa@in$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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