From: Ingo Molnar <mingo@elte.hu>
To: Paul Mundt <lethal@linux-sh.org>, Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] sparseirq: Enable early irq_desc allocation.
Date: Sat, 23 May 2009 14:57:48 +0200 [thread overview]
Message-ID: <20090523125748.GB23042@elte.hu> (raw)
In-Reply-To: <20090522014008.GA2806@linux-sh.org>
* Paul Mundt <lethal@linux-sh.org> wrote:
> On Thu, May 21, 2009 at 01:26:26PM -0700, Yinghai Lu wrote:
> > can you check tip?
> > we change _cpu to node already.
> >
> > also only sh have after_bootmem now.
> > arch/sh/mm/init.c:int after_bootmem = 0;
> > arch/sh/mm/init.c: after_bootmem = 1;
> > arch/sh/mm/ioremap_64.c: extern int after_bootmem;
> > arch/sh/mm/ioremap_64.c: if (after_bootmem) {
> > include/linux/mm.h:extern int after_bootmem;
> >
> > for x86 we have bootmem_state ...
> > arch/x86/include/asm/page_types.h:enum bootmem_state {
> > arch/x86/include/asm/page_types.h:extern enum bootmem_state bootmem_state;
> > arch/x86/kernel/setup.c: bootmem_state = DURING_BOOTMEM;
> > arch/x86/mm/init.c:enum bootmem_state bootmem_state = BEFORE_BOOTMEM;
> > arch/x86/mm/init.c: if (bootmem_state == BEFORE_BOOTMEM)
> > arch/x86/mm/init.c: if (bootmem_state == BEFORE_BOOTMEM)
> > arch/x86/mm/init.c: if (bootmem_state == BEFORE_BOOTMEM && !start) {
> > arch/x86/mm/init.c: if (bootmem_state == BEFORE_BOOTMEM &&
> > arch/x86/mm/init.c: if (bootmem_state == BEFORE_BOOTMEM)
> >
> > Andrew,
> > do we need to move bootmem_state back to linux/mm.h?
>
> No need, I just switched to slab_is_available() in the respin. Here is
> v2, against -tip:
thanks.
I'm a bit unhappy about allocators here (and this is not your
fault). There's not two but _three_ states for allocation: bootmem,
pagealloc, kmalloc. There is a (short) stage during bootup where
kmalloc is not enabled yet and bootmem is already deactivated. If we
ever use slab_is_available() in such a state it will blow up.
Fixing all this allocator bootstrapping mess we have in Linux is a
lot larger project though.
Ingo
next prev parent reply other threads:[~2009-05-23 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 16:56 Paul Mundt
2009-05-21 20:26 ` Yinghai Lu
2009-05-22 1:40 ` Paul Mundt
2009-05-23 12:57 ` Ingo Molnar [this message]
2009-05-23 12:57 ` [tip:irq/numa] sparseirq: Allow " tip-bot for Paul Mundt
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=20090523125748.GB23042@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=penberg@cs.helsinki.fi \
--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
all inboxes | Powered by JetHome®