From: Robert Picco <Robert.Picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PXM/Nid/SLIT patch
Date: Wed, 18 Feb 2004 18:56:48 +0000 [thread overview]
Message-ID: <4033B570.7090202@hp.com> (raw)
In-Reply-To: <40321CF7.5020301@hp.com>
Christoph Hellwig wrote:
>On Wed, Feb 18, 2004 at 10:33:29AM -0500, Robert Picco wrote:
>
>
>>This PXM value (255) isn't a SLIT or PXM defined quantity. It is really
>>specific to HP cell machines. For example, a machine configured with
>>two cells will report three PXMs. Two for the CPUs and one for the
>>interleaved memory at magic PXM 255. The firmware doesn't report SLIT
>>information for PXM 255. The patch approximates the SLIT value for PXM
>>255. I have attempted to arrive at code which doesn't break non-HP
>>hardware configurations. I have assumed the way the initialization code
>>was written that all NIDs require memory. Otherwise
>>reserve_pernode_space will fail.
>>
>>
>
>I know HP basically owns the IA64 ports, but honestly can't you fix
>the firmware to return sane information instead? i.e. move the above
>fix to firmware instead of letting linux fixup the reported data.
>
>
>
Well some of us would like to see this too. Some legacy requirements
from our other supported OSes require this to be the default
configuration. Perhaps a different default can be made in the future or
some IPMI tool to change the default.
next prev parent reply other threads:[~2004-02-18 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 13:53 PXM/Nid/SLIT patch Robert Picco
2004-02-17 22:32 ` Jesse Barnes
2004-02-18 15:33 ` Robert Picco
2004-02-18 17:08 ` Christoph Hellwig
2004-02-18 18:56 ` Robert Picco [this message]
2004-02-18 18:59 ` David Mosberger
2004-02-18 19:04 ` Jesse Barnes
2004-02-18 19:06 ` Jesse Barnes
2004-02-18 19:13 ` Christoph Hellwig
2004-02-18 19:19 ` Robert Picco
2004-02-18 19:36 ` Jesse Barnes
2004-02-18 19:43 ` David Mosberger
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=4033B570.7090202@hp.com \
--to=robert.picco@hp.com \
--cc=linux-ia64@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