From: keith <kmannth@us.ibm.com>
To: jamesclv@us.ibm.com
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>,
matt dobson <colpatch@us.ibm.com>,
Mike Kravetz <kravetz@us.ibm.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Anton Blanchard <anton@samba.org>,
Yasunori Goto <ygoto@us.fujitsu.com>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH 5/5] SRAT cleanup: make calculations and indenting level more sane
Date: Thu, 24 Feb 2005 14:02:58 -0800 [thread overview]
Message-ID: <1109282578.9817.1993.camel@knk> (raw)
In-Reply-To: <200502241249.54796.jamesclv@us.ibm.com>
On Thu, 2005-02-24 at 12:49, James Cleverdon wrote:
> No, I don't think we could rely on that. Our BIOS did ascending
> addresses, but I don't recall that being spelled out in the ACPI spec.
>
> Of course, there's a new ACPI spec out. Maybe it makes it a
> requirement. I'd take a look, but I can't afford the loss of sanity
> caused by gazing on the dread visage of ACPI 3.0. ;^)
The SRAT exists outside of the ACPI spec. It is something made up by
folks in Kirkland. I just reread the SRAT spec and I don't seen any
mention of requirements for linear order. Still yet we have yet to find
a box/bios version that breaks this assumption. All I know of is the IBM
summit boxes but maybe there is something else.
Maybe AMD x86_64 booting into 32 bit have SRATs as well?
Anyways maybe we could add some check to catch new hardware with less
friendly SRAT tables.
after the node_has_online_mem(nid) check
if (node_start_pfn[nid] > node_memory_chunk[j].start_pfn) {
printk (KERN_WARN "You need to rework the srat.c code\n");
continue;
}
Keith
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-02-24 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 17:29 [PATCH 5/5] SRAT cleanup: make calculations and indenting level more sane Dave Hansen
2005-02-24 19:30 ` keith
2005-02-24 19:54 ` Dave Hansen
2005-02-24 20:49 ` James Cleverdon
2005-02-24 22:02 ` keith [this message]
2005-02-24 22:56 ` James Cleverdon
2005-02-25 18:24 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 18:54 Dave Hansen
2005-02-28 18:54 ` Dave Hansen
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=1109282578.9817.1993.camel@knk \
--to=kmannth@us.ibm.com \
--cc=anton@samba.org \
--cc=apw@shadowen.org \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=jamesclv@us.ibm.com \
--cc=kravetz@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=ygoto@us.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.