From: Pavel Machek <pavel@suse.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org,
Michael Hanselmann <linux-kernel@hansmi.ch>,
Torrance <torrance123@gmail.com>, Michael Buesch <mb@bu3sch.de>,
linux-pm@lists.osdl.org
Subject: Re: [RFC 1/3] support powermac G5 CPU hotplug
Date: Tue, 12 Dec 2006 13:09:16 +0000 [thread overview]
Message-ID: <20061212130916.GB5190@ucw.cz> (raw)
In-Reply-To: <20061211230754.380263000@sipsolutions.net>
Hi!
> This patch allows "hotplugging" of CPUs on G5 machines. CPUs that are
> disabled are put into an idle loop with interrupts hard-disabled, to wake
> them up again we kick them just like when bringing them up.
>
> Maybe there's some way to actually turn off those CPUs even more?
>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> --- linux-2.6-git.orig/arch/powerpc/kernel/smp.c 2006-12-11 23:34:47.693716759 +0100
> +++ linux-2.6-git/arch/powerpc/kernel/smp.c 2006-12-11 23:37:55.017716759 +0100
> @@ -558,6 +558,9 @@ int __devinit start_secondary(void *unus
>
> local_irq_enable();
>
> + /* who knows what context the processor might have died in... */
> + task_thread_info(paca[cpu].__current)->preempt_count = 0;
> +
?? Context for downing cpu should better be well-defined. Just do this
in cpu_die if it is really required.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-12-12 13:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061211230208.526233000@sipsolutions.net>
2006-12-11 23:02 ` [RFC 1/3] support powermac G5 CPU hotplug Johannes Berg
2006-12-11 23:02 ` Johannes Berg
2006-12-11 23:02 ` [RFC 2/3] windfarm: dont die on suspend thread signal Johannes Berg
2006-12-11 23:02 ` Johannes Berg
2006-12-11 23:02 ` [RFC 3/3] suspend to disk on powermac G5 Johannes Berg
2006-12-11 23:02 ` Johannes Berg
2006-12-12 12:21 ` [RFC 0/3] experimental G5 powermac suspend implementation Johannes Berg
2006-12-12 13:22 ` [linux-pm] " Pavel Machek
2006-12-12 13:36 ` Johannes Berg
2006-12-12 14:07 ` [linux-pm] " Johannes Berg
2006-12-12 17:34 ` Gabriel Paubert
2006-12-13 12:37 ` Johannes Berg
[not found] ` <20061211230754.380263000@sipsolutions.net>
2006-12-12 13:09 ` Pavel Machek [this message]
2006-12-12 13:18 ` [linux-pm] [RFC 1/3] support powermac G5 CPU hotplug Johannes Berg
2006-12-12 13:47 ` Johannes Berg
2006-12-13 13:20 ` Johannes Berg
[not found] ` <20061211230754.679589000@sipsolutions.net>
2006-12-12 13:10 ` [RFC 2/3] windfarm: dont die on suspend thread signal Pavel Machek
2007-01-24 6:32 ` Benjamin Herrenschmidt
[not found] ` <20061211230754.979775000@sipsolutions.net>
2006-12-12 13:20 ` [linux-pm] [RFC 3/3] suspend to disk on powermac G5 Pavel Machek
2006-12-12 13:33 ` Johannes Berg
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=20061212130916.GB5190@ucw.cz \
--to=pavel@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@hansmi.ch \
--cc=linux-pm@lists.osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mb@bu3sch.de \
--cc=torrance123@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox