From: William Lee Irwin III <wli@holomorphy.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@zip.com.au
Subject: Re: 2.5.47 bootmem crash
Date: Mon, 18 Nov 2002 15:13:53 -0800 [thread overview]
Message-ID: <20021118231353.GS11776@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211182345421.2113-100000@serv>
On Mon, Nov 18, 2002 at 11:47:15PM +0100, Roman Zippel wrote:
Index: mm/page_alloc.c
===================================================================
RCS file: /home/linux-m68k/cvsroot/linux/mm/page_alloc.c,v
retrieving revision 1.1.1.36
diff -u -p -r1.1.1.36 page_alloc.c
--- mm/page_alloc.c 11 Nov 2002 19:12:51 -0000 1.1.1.36
+++ mm/page_alloc.c 18 Nov 2002 22:45:34 -0000
@@ -1181,7 +1181,7 @@ struct pglist_data contig_page_data = {
void __init free_area_init(unsigned long *zones_size)
{
- free_area_init_node(0, &contig_page_data, NULL, zones_size, 0, NULL);
+ free_area_init_node(0, &contig_page_data, NULL, zones_size, __pa(PAGE_OFFSET) >> PAGE_SHIFT, NULL);
mem_map = contig_page_data.node_mem_map;
}
#endif
---------- Roman Zippel's patch ends here ------------
This is a valid core fix for "memory doesn't start at zero", and will work
properly on all "memory starts at zero" machines without any overhead.
Thanks,
Bill
--
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/
parent reply other threads:[~2002-11-18 23:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.44.0211182345421.2113-100000@serv>]
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=20021118231353.GS11776@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=zippel@linux-m68k.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