From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Christian Kujau <lists@nerdbynature.de>,
LKML <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
xen-devel@lists.xensource.com
Subject: Re: WARNING: at mm/bootmem.c:535 alloc_arch_preferred_bootmem
Date: Wed, 1 Jul 2009 10:40:44 +0200 [thread overview]
Message-ID: <20090701084044.GB8171@elte.hu> (raw)
In-Reply-To: <1246427909.22417.7.camel@penberg-laptop>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Hi Jeremy,
>
> On Tue, 2009-06-30 at 13:59 -0700, Jeremy Fitzhardinge wrote:
> > > >From dc231c59194a973b80e6932bb4c162f2076635cb Mon Sep 17 00:00:00 2001
> > > From: Pekka Enberg <penberg@cs.helsinki.fi>
> > > Date: Tue, 30 Jun 2009 11:35:19 +0300
> > > Subject: [PATCH] xen: Use kcalloc() in xen_init_IRQ()
> > >
> > > The init_IRQ() function is now called with slab allocator initialized.
> > > Therefore, we must not use the bootmem allocator in xen_init_IRQ().
> > > Fixes the following boot-time warning:
> > >
> > > [ 0.000000] Linux version 2.6.30 (dummy@sid) (gcc version 4.4.0 (Debian 4.4.0-8) ) #1 Tue Jun 23 02:13:42 CEST 2009
> > > [ 0.000000] Command line: root=/dev/xvda1 console=hvc0 init=/sbin/init
> > > [ 0.000000] KERNEL supported cpus:
> > > [ 0.000000] Intel GenuineIntel
> > > [ 0.000000] AMD AuthenticAMD
> > > [ 0.000000] Centaur CentaurHauls
> > > [ 0.000000] BIOS-provided physical RAM map:
> > > [ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
> > > [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
> > > [ 0.000000] Xen: 0000000000100000 - 0000000008000000 (usable)
> > > [ 0.000000] DMI not present or invalid.
> > > [ 0.000000] last_pfn = 0x8000 max_arch_pfn = 0x400000000
> > > [ 0.000000] initial memory mapped : 0 - 20000000
> > >
> > > Reported-by: Christian Kujau <lists@nerdbynature.de>
> > > Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> >
> > Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>
> Thanks! Who should pick this patch up, btw? I think it ought to go
> to the xen subsystem tree (wherever that is).
Generally those fixes go via tip:x86/urgent - please send the patch
with a full changelog, the signoff and acked-by lines, etc.
Thanks,
Ingo
prev parent reply other threads:[~2009-07-01 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 3:01 Christian Kujau
2009-06-30 8:40 ` Pekka Enberg
2009-06-30 10:07 ` Christian Kujau
2009-06-30 20:59 ` Jeremy Fitzhardinge
2009-07-01 5:58 ` Pekka Enberg
2009-07-01 8:40 ` Ingo Molnar [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=20090701084044.GB8171@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=penberg@cs.helsinki.fi \
--cc=xen-devel@lists.xensource.com \
/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®