[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 8 Aug 2008 10:06:02 -0500
From: Cliff Wickman <cpw@....com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Vivek Goyal <vgoyal@...hat.com>, Keith Owens <kaos@....com.au>,
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>,
Bernhard Walle <bwalle@...e.de>
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger
On Fri, Aug 08, 2008 at 02:20:52PM +0200, Andi Kleen wrote:
> > In a partitioned system [I work for SGI, so I'm talking about an Altix],
> > there is memory sharing among multiple single-system images. And if
> > one of those partitions were to panic the other partitions need to
> > be informed that they cannot address the panic'd partition's memory.
> > (Once that partition is rebooted any such access will cause an MCA
> > in the accessor.)
>
> There are already existing shutdown hooks. Aren't they good enough
> for that?
For shutdown, yes. But on a panic crash_kexec() gets called
before the panic_notifier_list is run.
> I would feel uneasy about having arbitary drivers hook into panic().
> While I'm sure your code is great there is unfortunately a lot
> of crappy driver code around.
That is Eric Biederman's concern as well. But it seems we should
have a way for a user/customer to customize those events and their order,
as I noted in a previous post.
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@....com
(651) 683-3824
--
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