[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tip-7eccf7b227b6d3b1745b937ce35efc9c27f9b0e5@git.kernel.org>
Date: Wed, 6 May 2009 08:58:00 GMT
From: tip-bot for David Rientjes <rientjes@...gle.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
steiner@....com, yanmin_zhang@...ux.intel.com, tglx@...utronix.de,
rientjes@...gle.com, mingo@...e.hu
Subject: [tip:x86/urgent] x86, srat: do not register nodes beyond e820 map
Commit-ID: 7eccf7b227b6d3b1745b937ce35efc9c27f9b0e5
Gitweb: http://git.kernel.org/tip/7eccf7b227b6d3b1745b937ce35efc9c27f9b0e5
Author: David Rientjes <rientjes@...gle.com>
AuthorDate: Tue, 5 May 2009 12:50:02 -0700
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Wed, 6 May 2009 10:49:07 +0200
x86, srat: do not register nodes beyond e820 map
The mem= option will truncate the memory map at a specified address so
it's not possible to register nodes with memory beyond the e820 upper
bound.
unparse_node() is only called when then node had memory associated with
it, although with the mem= option it is no longer addressable.
[ Impact: fix boot hang on certain (large) systems ]
Reported-by: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Signed-off-by: David Rientjes <rientjes@...gle.com>
Acked-by: Jack Steiner <steiner@....com>
LKML-Reference: <alpine.DEB.2.00.0905051248150.20021@...no.kir.corp.google.com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
arch/x86/mm/srat_64.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/mm/srat_64.c b/arch/x86/mm/srat_64.c
index 33c5fa5..0176595 100644
--- a/arch/x86/mm/srat_64.c
+++ b/arch/x86/mm/srat_64.c
@@ -361,6 +361,7 @@ static void __init unparse_node(int node)
{
int i;
node_clear(node, nodes_parsed);
+ node_clear(node, cpu_nodes_parsed);
for (i = 0; i < MAX_LOCAL_APIC; i++) {
if (apicid_to_node[i] == node)
apicid_to_node[i] = NUMA_NO_NODE;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists