public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alan@redhat.com
Subject: Re: [PATCH] Double x86 initialise fix.
Date: 26 Oct 2002 08:08:46 -0600	[thread overview]
Message-ID: <m1fzutl2c1.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20021026134947.GA31349@suse.de>

Dave Jones <davej@codemonkey.org.uk> writes:

> On Sat, Oct 26, 2002 at 02:56:20PM +0100, Alan Cox wrote:
>  > > For many moons, we've been executing identify_cpu()
>  > > on the boot processor twice on SMP kernels.
>  > > This is harmless, but has a few downsides..
>  > > - Extra cruft in bootlog/dmesg
>  > > - Spawns one too many timers for the mcheck handler
>  > > - possibly other wasteful things..
>  > > 
>  > > This seems to do the right thing here..
> 
> Isn't this always the case on x86 ?
> /me waits to hear gory details of some IBM monster.

If it is the logical cpu id yes, then id 0 is always the bootstrap
cpu.

For apic id #0 to not be the bootstrap cpu you don't need an IBM
monster, there are several SMP machines with that property.

Eric

      parent reply	other threads:[~2002-10-26 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 12:42 [PATCH] Double x86 initialise fix davej
2002-10-26 13:56 ` Alan Cox
2002-10-26 13:49   ` Dave Jones
2002-10-26 13:57     ` Alan Cox
2002-10-26 15:00       ` Martin J. Bligh
2002-10-26 15:03         ` Martin J. Bligh
2002-10-26 15:46         ` Alan Cox
2002-10-28 19:57           ` Zwane Mwaikambo
2002-10-26 14:08     ` Eric W. Biederman [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=m1fzutl2c1.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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