From: keith mannthey <kmannth@us.ibm.com>
To: Dave Jones <davej@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] patch [1/1] convert i386 summit subarch to use SRAT data for apicid_to_node
Date: Wed, 21 Jun 2006 20:55:51 -0700 [thread overview]
Message-ID: <1150948551.10001.62.camel@keithlap> (raw)
In-Reply-To: <20060622022414.GB4449@redhat.com>
On Wed, 2006-06-21 at 22:24 -0400, Dave Jones wrote:
> On Wed, Jun 21, 2006 at 06:54:55PM -0700, keith mannthey wrote:
> > Hello All,
> > This patch converts the i386 summit subarch apicid_to_node to use node
> > information provided by the SRAT. The current way of obtaining the
> > nodeid
> >
> > static inline int apicid_to_node(int logical_apicid)
> > {
> > return logical_apicid >> 5;
> > }
> >
> > is just not correct for all summit systems/bios. Assuming the apicid
> > matches the Linux node number require a leap of faith that the bios lay-
> > ed out the apicids a set way. Modern summit HW does not layout its bios
> > in the manner for various reasons and is unable to boot i386 numa.
> >
> > The best way to get the correct apicid to node information is from the
> > SRAT table.
>
> Do all summit's have SRAT tables ?
> I was under the impression the early ones were around before
> the invention of SRAT.
That is a good point. Let me check into the x440 (1st gen). x445 x460
(2nd,3rd gen) uses SRAT for sure (these patches have been tested on
these systems).
The x440 lists an srat but maybe it is using some special bios area. I
will build a test kernel give it a whirl.
> Dave
>
--
keith mannthey <kmannth@us.ibm.com>
Linux Technology Center IBM
next prev parent reply other threads:[~2006-06-22 3:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 1:54 [RFC] patch [1/1] convert i386 summit subarch to use SRAT data for apicid_to_node keith mannthey
2006-06-22 2:24 ` Dave Jones
2006-06-22 3:55 ` keith mannthey [this message]
2006-06-22 6:36 ` Martin J. Bligh
2006-06-22 19:21 ` keith mannthey
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=1150948551.10001.62.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=davej@redhat.com \
--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