[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080807221106.734a8da3@kopernikus.site>
Date: Thu, 7 Aug 2008 22:11:06 +0200
From: Bernhard Walle <bwalle@...e.de>
To: Andi Kleen <andi@...stfloor.org>
Cc: Jay Lan <jlan@....com>,
Christoph Lameter <cl@...ux-foundation.org>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Nick Piggin <nickpiggin@...oo.com.au>,
jmerkey@...fmountaingroup.com,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Josh Boyer <jwboyer@...il.com>, linux-kernel@...r.kernel.org,
Takenori Nagano <t-nagano@...jp.nec.com>,
Vivek Goyal <vgoyal@...hat.com>, Keith Owens <kaos@....com.au>
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger
* Andi Kleen <andi@...stfloor.org> [2008-08-07 22:09]:
>
> On Thu, Aug 07, 2008 at 10:07:37PM +0200, Bernhard Walle wrote:
> > * Andi Kleen <andi@...stfloor.org> [2008-08-07 22:06]:
> > >
> > > > To merge KDB or any other RAS tools, you need to deal with kdump. Kdump
> > > > hijack panic() before the die calling chain. For KDB or a RAS tool to
> > >
> > > Imho kdump should just be fixed to use die chains.
> >
> > Well, we had that discussion several times. I'm not against it
> > (instead, I would like it), but I don't think that repeating the
> > discussion over and over does help ...
>
> Just needs some code?
No, it was rejected with the argument that in panic case, as less code
as possible should be executed before kexec'ing the panic kernel.
See also: http://kerneltrap.org/node/14050 (for example)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--
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/
Powered by blists - more mailing lists