From: Ingo Molnar <mingo@elte.hu>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Mel Gorman <mel@csn.ul.ie>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH 0/2] panics booting NUMA SPARSEMEM on x86_32 NUMA
Date: Tue, 20 May 2008 14:08:55 +0200 [thread overview]
Message-ID: <20080520120855.GA10080@elte.hu> (raw)
In-Reply-To: <exportbomb.1211277639@pinky>
* Andy Whitcroft <apw@shadowen.org> wrote:
> We have been seeing panics booting NUMA SPARSEMEM kernels on x86_32
> hardware, while trying to allocate node local memory in early boot.
> These are caused by a miss-allocation of the node pgdat structures
> when numa remap is disabled.
>
> Following this email are two patches, the first reenables numa remap
> for SPARSEMEM as the underlying bug has now been fixed. The second
> hardens the pgdat allocation in the face of there being no numa remap
> for a particular node (which may still occur).
applied to -tip, thanks Andy.
Ingo
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-05-20 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 10:00 [PATCH 0/2] panics booting NUMA SPARSEMEM on x86_32 NUMA Andy Whitcroft
2008-05-20 10:01 ` [PATCH 1/2] x86: reinstate numa remap for SPARSEMEM on x86 NUMA systems Andy Whitcroft
2008-05-20 10:01 ` [PATCH 2/2] x86: cope with no remap space being allocated for a numa node Andy Whitcroft
2008-05-20 12:08 ` 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=20080520120855.GA10080@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).