From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: ego@in.ibm.com
Cc: Gautham Shenoy <ego.lkml@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [RFC][PATCH][EXPERIMENTAL] CPU hotplug with frozen tasks
Date: Wed, 18 Apr 2007 19:07:09 +0200 [thread overview]
Message-ID: <200704181907.10288.rjw@sisk.pl> (raw)
In-Reply-To: <20070418094211.GC6474@in.ibm.com>
On Wednesday, 18 April 2007 11:42, Gautham R Shenoy wrote:
> Hi,
>
> The patch looks good to me.
>
> On Mon, Apr 16, 2007 at 11:27:58PM +0200, Rafael J. Wysocki wrote:
> >
> > ---
> > Documentation/cpu-hotplug.txt | 9 +++++++--
> > arch/i386/kernel/cpu/intel_cacheinfo.c | 2 ++
> > arch/i386/kernel/cpu/mcheck/therm_throt.c | 2 ++
> > arch/i386/kernel/cpuid.c | 2 ++
>
> [snip]
>
> Though I am wondering what might be the usecase for microcode!
Well, for 2.6.21-rc I had to introduce the variable suspend_cpu_hotplug (in
cpu.c) and make the microcode driver use it to distinguish between the 'normal'
and suspend-related CPU hotplug. I'd like to get rid of this ugliness ASAP.
> Guess we'll see that patch soon :-)
Yes, in a couple of days. I have to make both patches apply to -mm first. :-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-04-18 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 15:32 [RFD] CPU hotplug and suspend Rafael J. Wysocki
2007-04-06 15:56 ` Eric W. Biederman
2007-04-09 14:03 ` Pavel Machek
2007-04-09 13:14 ` Rafael J. Wysocki
2007-04-16 7:01 ` Pavel Machek
2007-04-15 22:27 ` [RFC][PATCH][EXPERIMENTAL] CPU hotplug with frozen tasks Rafael J. Wysocki
2007-04-16 7:05 ` Pavel Machek
2007-04-16 21:06 ` Rafael J. Wysocki
2007-04-16 9:50 ` Gautham Shenoy
2007-04-16 21:27 ` Rafael J. Wysocki
2007-04-18 9:42 ` Gautham R Shenoy
2007-04-18 17:07 ` Rafael J. Wysocki [this message]
2007-04-23 19:19 ` Oleg Nesterov
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=200704181907.10288.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ego.lkml@gmail.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
--cc=vatsa@in.ibm.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
Powered by JetHome