public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	Linus Torvalds <torvalds@transmeta.com>,
	davidm@hpl.hp.com, ralf@gnu.org, paulus@samba.org,
	anton@samba.org, schwidefsky@de.ibm.com, ak@suse.de,
	davem@redhat.com
Subject: Re: [PATCH] 2.5.25 Hotplug CPU boot changes
Date: Tue, 16 Jul 2002 10:48:26 +1000	[thread overview]
Message-ID: <20020716005809.D5F1E4599@lists.samba.org> (raw)
In-Reply-To: Your message of "15 Jul 2002 13:29:01 +0100." <1026736141.13885.105.camel@irongate.swansea.linux.org.uk>

In message <1026736141.13885.105.camel@irongate.swansea.linux.org.uk> you write
:
> On Mon, 2002-07-15 at 09:58, Rusty Russell wrote:
> > The following patches change boot sequence, and once Linus releases
> > 2.5.26, I'll be updating and sending them.  This will break every SMP
> > architecture (patch for x86 below, and I have a patch for PPC32).
> >			printk("ksoftirqd for %i failedn", hotcpu);
> 
> Q: What prevents a CPU coming up -during- an MTRR change once the rest
> of the cpu hot plugging is present ?

Nothing, that's (one of the reasons) why cpu hotplug is not
implemented on x86.

[ Disclosure: I tried to rewrite the x86 boot code to actually bring
  CPUs up one at a time, rather than the minimal wedge seen in this
  patch, and failed.  Me no x86-pert, and the boot code is hairy. ]

I'm still considering a big reader lock around the actual bringing up
of CPUs, pending me completing my audit of what code actually needs
this (surprisingly, very little generic code actually cares how many
CPUs we have, so it's mainly a few corner cases).  This would be
cheap, and allow code that cared to lock out cpu changes.

Thoughts?
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      parent reply	other threads:[~2002-07-16  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  8:58 [PATCH] 2.5.25 Hotplug CPU boot changes Rusty Russell
2002-07-15 12:29 ` Alan Cox
2002-07-15 15:23   ` Dave Jones
2002-07-16  0:48   ` Rusty Russell [this message]

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=20020716005809.D5F1E4599@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=ralf@gnu.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=torvalds@transmeta.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