From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <clameter@sgi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andre Noll <maan@systemlinux.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22-rc7
Date: Tue, 3 Jul 2007 21:45:23 +0200 [thread overview]
Message-ID: <20070703194523.GC493@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0707030921400.4810@schroedinger.engr.sgi.com>
* Christoph Lameter <clameter@sgi.com> wrote:
> > However, it might be worth avoiding the warning, even if it seems
> > bogus in this case. Christoph? Do you agree with the analysis? And
> > the patch might be as simple as changing
> > early_kmem_cache_node_alloc() to enable interrupts at the _end_ of
> > the function, rather than immediately after calling new_slab().
>
> new_slab() enables and disables interrupts during usual operations.
> During bootstrap interrupts are enabled and so new_slab() falsely
> disables interrupts when we do the alloc by hand thing in
> early_kmem_cache_node_alloc for NUMA. We need to enable interrupts
> there since otherwise boot will continue with interrupts disabled.
yeah. Your change looks good to me. You could add a
local_irq_enable_in_hardirq() to the original place, that will map to a
local_irq_enable() on non-lockdep kernels and will be a NOP on lockdep
kernels. (This is a bit hacky though.)
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2007-07-03 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 21:32 Linux 2.6.22-rc7 Linus Torvalds
2007-07-03 15:55 ` Andre Noll
2007-07-03 16:17 ` Linus Torvalds
2007-07-03 16:31 ` Christoph Lameter
2007-07-03 16:46 ` Andre Noll
2007-07-03 19:45 ` Ingo Molnar [this message]
2007-07-03 19:52 ` Christoph Lameter
2007-07-03 20:19 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-07-03 16:14 Martin Knoblauch
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=20070703194523.GC493@elte.hu \
--to=mingo@elte.hu \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.