From: Russ Anderson <rja@sgi.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, "H. Peter Anvin" <h.peter.anvin@intel.com>,
Jack Steiner <steiner@sgi.com>,
rja@americas.sgi.com
Subject: Re: [BUG] x86: bootmem broken on SGI UV
Date: Sat, 9 Oct 2010 07:59:45 -0500 [thread overview]
Message-ID: <20101009125944.GA18248@sgi.com> (raw)
In-Reply-To: <4CAFA1DB.6010802@kernel.org>
Yes, Yinghai's patch fixes the problem.
Thank you very much.
On Fri, Oct 08, 2010 at 03:57:31PM -0700, Yinghai Lu wrote:
> On 10/08/2010 02:34 PM, Russ Anderson wrote:
>
> After looking at the changelog, it turns out it is broken for a while by
> following commit
>
> |commit 8716273caef7f55f39fe4fc6c69c5f9f197f41f1
> |Author: David Rientjes <rientjes@google.com>
> |Date: Fri Sep 25 15:20:04 2009 -0700
> |
> | x86: Export srat physical topology
>
> before that commit, register_active_regions() is called SRAT memory entries.
>
> Try to use nodememblk_range[] instead of nodes[].
>
> For stable tree: from 2.6.33 to 2.3.36 need this patch by
> changing memblock_x86_register_active_regions() with e820_register_active_regions()
>
> Reported-by: Russ Anderson <rja@sgi.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Cc: stable@kernel.org
>
> ---
> arch/x86/mm/srat_64.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> Index: linux-2.6/arch/x86/mm/srat_64.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/mm/srat_64.c
> +++ linux-2.6/arch/x86/mm/srat_64.c
> @@ -421,9 +421,11 @@ int __init acpi_scan_nodes(unsigned long
> return -1;
> }
>
> - for_each_node_mask(i, nodes_parsed)
> - memblock_x86_register_active_regions(i, nodes[i].start >> PAGE_SHIFT,
> - nodes[i].end >> PAGE_SHIFT);
> + for (i = 0; i < num_node_memblks; i++)
> + memblock_x86_register_active_regions(memblk_nodeid[i],
> + node_memblk_range[i].start >> PAGE_SHIFT,
> + node_memblk_range[i].end >> PAGE_SHIFT);
> +
> /* for out of order entries in SRAT */
> sort_node_map();
> if (!nodes_cover_memory(nodes)) {
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2010-10-09 12:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 21:34 Russ Anderson
2010-10-08 21:43 ` H. Peter Anvin
2010-10-08 22:15 ` Yinghai Lu
2010-10-08 22:57 ` Yinghai Lu
2010-10-09 12:59 ` Russ Anderson [this message]
2010-10-09 16:39 ` Robin Holt
2010-10-09 18:06 ` Yinghai Lu
2010-10-09 18:17 ` [PATCH -v2] x86, numa: Fix cross nodes memory configuration Yinghai Lu
2010-10-09 18:39 ` [BUG] x86: bootmem broken on SGI UV Linus Torvalds
2010-10-10 10:41 ` Ingo Molnar
2010-10-10 10:43 ` Ingo Molnar
2010-10-10 11:44 ` Robin Holt
2010-10-10 11:56 ` Robin Holt
2010-10-10 14:05 ` Ingo Molnar
2010-10-10 22:51 ` Robin Holt
2010-10-11 2:52 ` [PATCH -v3] x86, numa: Fix cross nodes memory configuration Yinghai Lu
2010-10-11 22:01 ` [tip:x86/urgent] x86, numa: For each node, register the memory blocks actually used tip-bot for Yinghai Lu
2010-10-11 22:05 ` David Rientjes
2010-10-11 22:21 ` H. Peter Anvin
2010-10-11 22:28 ` tip-bot for Yinghai Lu
2010-10-10 1:04 [BUG] x86: bootmem broken on SGI UV Anvin, H Peter
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=20101009125944.GA18248@sgi.com \
--to=rja@sgi.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rja@americas.sgi.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome