From: Rusty Russell <rusty@rustcorp.com.au>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Andrew Morton <akpm@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
LHCS list <lhcs-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Hotplug CPU toy for i386
Date: Thu, 25 Mar 2004 15:33:22 +1100 [thread overview]
Message-ID: <1080189202.25555.26.camel@bach> (raw)
In-Reply-To: <Pine.LNX.4.58.0403220153520.28727@montezuma.fsmlabs.com>
On Mon, 2004-03-22 at 20:56, Zwane Mwaikambo wrote:
> On Mon, 22 Mar 2004, Rusty Russell wrote:
>
> > @@ -1035,6 +1036,10 @@ inline void smp_local_timer_interrupt(st
> > {
> > int cpu = smp_processor_id();
> >
> > + /* FIXME: Actually remove timer interrupt in __cpu_disable() --RR */
> > + if (cpu_is_offline(cpu))
> > + return;
> > +
>
> We could setup an offline cpu idt with nop type interrupt stubs, this
> could also take care of the irq_stabilizing problem later on...
The problem I have with this approach is that it shouldn't be
neccessary. Perhaps I'm overly optimistic.
I know *nothing* about i386: I'll play with stealing the PM code's
APIC suspend/resume, which I think is the Right Way to do this.
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-03-25 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <405C1F42.9030901@cyberone.com.au>
2004-03-22 6:34 ` [PATCH] Hotplug CPU toy for i386 Rusty Russell
2004-03-22 9:56 ` Zwane Mwaikambo
2004-03-25 4:33 ` Rusty Russell [this message]
2004-03-30 12:21 ` Pavel Machek
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=1080189202.25555.26.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=lhcs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=zwane@linuxpower.ca \
/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