public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	manpreet@fabric7.com,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org
Subject: Re: [PATCH] i386/x86-64: Fix timer SMP bootup race
Date: Sat, 15 Jan 2005 08:59:46 +0100	[thread overview]
Message-ID: <20050115075946.GA28981@wotan.suse.de> (raw)
In-Reply-To: <1105774495.12263.21.camel@localhost.localdomain>

On Sat, Jan 15, 2005 at 06:34:54PM +1100, Rusty Russell wrote:
> > I shortly considered redoing the boot process, but then it looked 
> > too risky to me. 
> > 
> > e.g. I guess on x86-64 it wouldn't be that difficult, just a bit of work,
> > but on i386 with all the weird hardware it could be quite destabilizing.
> > But doing it on x86-64 only is not a good solution.
> 
> Well, architectures which support CPU hotplug have had to fix their boot
> process anyway, and most are fairly trivial.

The problem is not doing the work, but testing it.

> > If you had done it properly in 2.5 it would be working and tested
> > by now ;-) , but doing it in the middle of 2.6 would seem a bit misplaced
> > to me.
> 
> Linus would not have taken the patch, because it would have broken too
> much.  Cleaning up the x86 boot sequence is a project in itself, which
> needs to be done, but not by me 8)

I think my patch is better. It at least keeps all the 
baggage out of the normal run paths. Doing this check at each timer interrupt
doesn't make much sense.

-Andi

  parent reply	other threads:[~2005-01-15  8:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15  4:09 [PATCH] i386/x86-64: Fix timer SMP bootup race Andi Kleen
2005-01-15  5:09 ` Rusty Russell
2005-01-15  5:23   ` Andi Kleen
2005-01-15  7:34     ` Rusty Russell
2005-01-15  7:40       ` Andrew Morton
2005-01-15  7:59       ` Andi Kleen [this message]
2005-01-16  4:20         ` Rusty Russell
2005-01-16  5:34           ` Andi Kleen
2005-01-16  6:42             ` Rusty Russell
2005-01-15  6:28 ` Andrew Morton
2005-01-15  6:43   ` Andi Kleen
2005-01-15  6:54     ` Andrew Morton
2005-01-15  7:18       ` Andi Kleen
2005-01-17  2:34 ` Rusty Russell
2005-01-17  5:43   ` Andi Kleen

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=20050115075946.GA28981@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manpreet@fabric7.com \
    --cc=rusty@rustcorp.com.au \
    /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