--Sonny Rao <[EMAIL PROTECTED]> wrote (on Monday, August 01, 2005 02:23:22
-0400):
> On Mon, Aug 01, 2005 at 12:27:42AM -0500, Paul Mackerras wrote:
>> From: Mike Kravetz <[EMAIL PROTECTED]>
>>
>> If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
>> because of special
--Sonny Rao [EMAIL PROTECTED] wrote (on Monday, August 01, 2005 02:23:22
-0400):
On Mon, Aug 01, 2005 at 12:27:42AM -0500, Paul Mackerras wrote:
From: Mike Kravetz [EMAIL PROTECTED]
If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
because of special processing
On Mon, Aug 01, 2005 at 12:27:42AM -0500, Paul Mackerras wrote:
> From: Mike Kravetz <[EMAIL PROTECTED]>
>
> If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
> because of special processing needed to handle invalid node IDs (0x)
> on POWER 4. My previous patch to
On Mon, Aug 01, 2005 at 12:27:42AM -0500, Paul Mackerras wrote:
From: Mike Kravetz [EMAIL PROTECTED]
If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
because of special processing needed to handle invalid node IDs (0x)
on POWER 4. My previous patch to handle
From: Mike Kravetz <[EMAIL PROTECTED]>
If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
because of special processing needed to handle invalid node IDs (0x)
on POWER 4. My previous patch to handle memory 'holes' within nodes
forgot to add this special case for POWER 4
From: Mike Kravetz [EMAIL PROTECTED]
If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
because of special processing needed to handle invalid node IDs (0x)
on POWER 4. My previous patch to handle memory 'holes' within nodes
forgot to add this special case for POWER 4 in
6 matches
Mail list logo