From: Alan Cox <alan@redhat.com>
To: davej@codemonkey.org.uk (Dave Jones)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
alan@redhat.com
Subject: Re: [PATCH] Double x86 initialise fix.
Date: Sat, 26 Oct 2002 09:57:42 -0400 (EDT) [thread overview]
Message-ID: <200210261357.g9QDvgl13774@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021026134947.GA31349@suse.de> from "Dave Jones" at Oct 26, 2002 02:49:47 PM
> Isn't this always the case on x86 ?
> /me waits to hear gory details of some IBM monster.
It isnt. The boot CPU may be any number. In addition you can strap dual
pentium boxes to arbitrate for who is boot cpu (this is used for fault
tolerance).
next prev parent reply other threads:[~2002-10-26 13:51 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 [this message]
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
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=200210261357.g9QDvgl13774@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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