From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH] x86, mm: Skip unknown PXM early in SLIT parsing
Date: Mon, 21 Jan 2013 13:33:57 -0800 [thread overview]
Message-ID: <1358804037-29244-1-git-send-email-yinghai@kernel.org> (raw)
Some systems one bios could support 2 sockets and 4 sockets,
and SLIT is the same, aka 4x4.
For 2 sockets configuration, SRAT will only have PXM0 and PXM2.
So we will get warning:
NUMA: Warning: node ids are out of bound, from=0 to=-1 distance=15
Need to skip PXM1 and PXM2 as there is no responding node,
To avoid uncorrect warning.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
arch/x86/mm/srat.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
Index: linux-2.6/arch/x86/mm/srat.c
===================================================================
--- linux-2.6.orig/arch/x86/mm/srat.c
+++ linux-2.6/arch/x86/mm/srat.c
@@ -46,11 +46,22 @@ static __init inline int srat_disabled(v
void __init acpi_numa_slit_init(struct acpi_table_slit *slit)
{
int i, j;
+ int from_node, to_node;
- for (i = 0; i < slit->locality_count; i++)
- for (j = 0; j < slit->locality_count; j++)
- numa_set_distance(pxm_to_node(i), pxm_to_node(j),
+ for (i = 0; i < slit->locality_count; i++) {
+ from_node = pxm_to_node(i);
+ if (from_node < 0)
+ continue; /* skip unknown PXM */
+
+ for (j = 0; j < slit->locality_count; j++) {
+ to_node = pxm_to_node(j);
+ if (to_node < 0)
+ continue; /* skip unknown PXM */
+
+ numa_set_distance(from_node, to_node,
slit->entry[slit->locality_count * i + j]);
+ }
+ }
}
/* Callback for Proximity Domain -> x2APIC mapping */
reply other threads:[~2013-01-21 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1358804037-29244-1-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®