From: James Cleverdon <jamesclv@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>,
<linux-kernel@vger.kernel.org>,
"Marcelo Tosatti" <marcelo@conectiva.com.br>
Subject: Re: [PATCH] 2.4.23-rc1: cpu_sibling_map fix
Date: Thu, 13 Nov 2003 14:13:37 -0800 [thread overview]
Message-ID: <200311131413.37223.jamesclv@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173618737@scsmsx402.sc.intel.com>
On Thursday 13 November 2003 11:32 am, Nakajima, Jun wrote:
> Can you please explain why the information by CPUID does not work for
> summit-based machine? The CPUID does not reflect the H/W configuration,
> and the BIOS needs to communicate via local APIC Ids instead?
>
> Jun
Easy. Note this bit from Intel's IA-32 manual:
* Local APIC ID (high byte of EBX)--this number is the 8-bit ID that is
assigned to the local APIC on the processor during power up. This
field was introduced in the Pentium 4 processor.
On almost all systems, the value latched in the CPU when it comes out of reset
doesn't change over the life of the system. However, our Summit boxes (and I
suspect most NUMA boxen) have a BIOS that builds the full system out of
smaller building blocks, each of which starts as an independent computer.
The act of doing so means rewriting the local APIC ID register with a
different value. (It turns out that the CPU only latches 6 bits of APIC ID,
but we need 8.)
Thus, we need the patch that reads the APIC ID register instead of just using
the value from cpuid. And we probably won't be the only ones either.
> > -----Original Message-----
[ Snip! ]
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot comm
next prev parent reply other threads:[~2003-11-13 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 19:32 Nakajima, Jun
2003-11-13 22:13 ` James Cleverdon [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 3:56 James Cleverdon
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=200311131413.37223.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
Powered by JetHome