From: "Michael Ellerman" <michael@ellerman.id.au>
To: ljhc@br.ibm.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Christoph Lameter" <clameter@sgi.com>,
"Arnd Bergmann" <arndb@arndb.de>,
cbe-oss-dev@ozlabs.org
Subject: Re: SLUB doesn't work with kdump kernel on Cell
Date: Fri, 10 Aug 2007 10:34:46 +1000 [thread overview]
Message-ID: <dc1166600708091734p22612a72g7fcc3e229203918f@mail.gmail.com> (raw)
In-Reply-To: <1186667828.3038.18.camel@localhost.localdomain>
On 8/9/07, Lucio Correia <ljhc@br.ibm.com> wrote:
> On Wed, 2007-08-08 at 23:10 +0200, Arnd Bergmann wrote:
> > On Wednesday 08 August 2007, Lucio Correia wrote:
> > > DMA 0 -> 12288
> > > Normal 12288 -> 12288
> > > early_node_map[2] active PFN ranges
> > > 0: 0 -> 2560
> > > 1: 12287 -> 12288
> >
> > As Christoph found, this memory map is really strange. Other machines
> > have something like
> >
> > Zone PFN ranges:
> > DMA 0 -> 16384
> > Normal 16384 -> 16384
> > early_node_map[2] active PFN ranges
> > 0: 0 -> 8192
> > 1: 8192 -> 16384
> >
> > Lucio,
> > What code builds the memory map that gets passed to the kdump kernel?
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.
> I also tried to pass maxcpus=1 for the command line of second kernel,
> and it didn't work. How can I alternatively disable the node?
maxcpus is poorly tested and is known to be broken on Cell, please
don't use it, or fix it first :)
cheers
next prev parent reply other threads:[~2007-08-10 0:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 20:15 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 [this message]
2007-08-10 15:43 ` [Cbe-oss-dev] " Arnd Bergmann
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=dc1166600708091734p22612a72g7fcc3e229203918f@mail.gmail.com \
--to=michael@ellerman.id.au \
--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 \
/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®