From: Andi Kleen <ak@suse.de>
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu
Subject: Re: [PATCH] Disable useless bootmem warning
Date: Mon, 16 Feb 2004 20:13:34 +0100 [thread overview]
Message-ID: <20040216201334.07ab2aa8.ak@suse.de> (raw)
In-Reply-To: <20040216165211.GC2389@phunnypharm.org>
On Mon, 16 Feb 2004 11:52:11 -0500
Ben Collins <bcollins@debian.org> wrote:
> > I've never seen a bug uncovered by this warning too. I considered to disable it
> > by passing a special array of "ok to reserve twice" regions, but on second thought
> > it is just best to remove it completely. Reserving things twice is not usually
> > an error.
>
> I have. When I was working to get sparc64 booting from alternate memory
> (other than 0x0 physical), those messages helped me a lot.
>
> Maybe make it ifdef'd by CONFIG_DEBUG_BOOTMEM (which is an option that I
> know sparc and sparc64 already have).
That would be fine by me too. Anything, as long as I don't have to see them ;-)
Here's a new patch.
-Andi
diff -u linux-2.6.2-work32/mm/bootmem.c-o linux-2.6.2-work32/mm/bootmem.c
--- linux-2.6.2-work32/mm/bootmem.c-o 2004-02-11 22:06:58.000000000 +0100
+++ linux-2.6.2-work32/mm/bootmem.c 2004-02-16 20:11:10.000000000 +0100
@@ -91,8 +91,11 @@
if (end > bdata->node_low_pfn)
BUG();
for (i = sidx; i < eidx; i++)
- if (test_and_set_bit(i, bdata->node_bootmem_map))
+ if (test_and_set_bit(i, bdata->node_bootmem_map)) {
+#ifdef CONFIG_DEBUG_BOOTMEM
printk("hm, page %08lx reserved twice.\n", i*PAGE_SIZE);
+#endif
+ }
}
static void __init free_bootmem_core(bootmem_data_t *bdata, unsigned long addr, unsigned long size)
prev parent reply other threads:[~2004-02-16 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 17:00 [PATCH] Disable useless bootmem warning Andi Kleen
2004-02-16 16:52 ` Ben Collins
2004-02-16 19:13 ` Andi Kleen [this message]
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=20040216201334.07ab2aa8.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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