public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: cbe-oss-dev@ozlabs.org
Cc: "Michael Ellerman" <michael@ellerman.id.au>,
	ljhc@br.ibm.com, Arnd Bergmann <arndb@arndb.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [Cbe-oss-dev] SLUB doesn't work with kdump kernel on Cell
Date: Fri, 10 Aug 2007 17:43:33 +0200	[thread overview]
Message-ID: <200708101743.34988.arnd@arndb.de> (raw)
In-Reply-To: <dc1166600708091734p22612a72g7fcc3e229203918f@mail.gmail.com>

On Friday 10 August 2007, Michael Ellerman wrote:
> It comes out of the device tree, just like a regular kernel. The
> device tree for the kdump kernel is built by kexec-tools, it parses
> /proc/device-tree and does a bunch of logic to avoid various reserved
> regions: the kernel, TCE tables, RTAS etc.

Maybe it should then try to flatten out the NUMA properties and put
all pages logically into the same node that the boot CPU resides on.
I can see a number of things going wrong otherwise.

	Arnd <><

  reply	other threads:[~2007-08-10 17:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 20:15 SLUB doesn't work with kdump kernel on Cell Lucio Correia
2007-08-08 20:26 ` Christoph Lameter
2007-08-08 20:34   ` Arnd Bergmann
2007-08-08 20:39     ` Christoph Lameter
2007-08-14 15:43   ` Lucio Correia
2007-08-14 19:42     ` Christoph Lameter
2007-08-15  0:57       ` Michael Ellerman
2007-08-15  1:56         ` Christoph Lameter
2007-08-15  2:11         ` Christoph Lameter
2007-08-15 19:57           ` Lucio Correia
2007-08-15 20:21             ` Christoph Lameter
2007-08-08 21:10 ` Arnd Bergmann
2007-08-09 13:57   ` Lucio Correia
2007-08-10  0:34     ` Michael Ellerman
2007-08-10 15:43       ` Arnd Bergmann [this message]
2007-08-10  0:26   ` Michael Ellerman

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=200708101743.34988.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=arndb@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljhc@br.ibm.com \
    --cc=michael@ellerman.id.au \
    /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