linux-kernel - Re: SLUB doesn't work with kdump kernel on Cell

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dc1166600708091734p22612a72g7fcc3e229203918f@mail.gmail.com>
Date:	Fri, 10 Aug 2007 10:34:46 +1000
From:	"Michael Ellerman" <michael@...erman.id.au>
To:	ljhc@...ibm.com
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	"Christoph Lameter" <clameter@....com>,
	"Arnd Bergmann" <arndb@...db.de>, cbe-oss-dev@...abs.org
Subject: Re: SLUB doesn't work with kdump kernel on Cell

On 8/9/07, Lucio Correia <ljhc@...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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/