From: Andi Kleen <andi@firstfloor.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>, Keith Owens <kaos@ocs.com.au>,
Jay Lan <jlan@sgi.com>,
Christoph Lameter <cl@linux-foundation.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Nick Piggin <nickpiggin@yahoo.com.au>,
jmerkey@wolfmountaingroup.com,
Geert Uytterhoeven <geert@linux-m68k.org>,
Josh Boyer <jwboyer@gmail.com>,
linux-kernel@vger.kernel.org,
Takenori Nagano <t-nagano@ah.jp.nec.com>,
Bernhard Walle <bwalle@suse.de>
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger
Date: Fri, 8 Aug 2008 20:03:03 +0200 [thread overview]
Message-ID: <20080808180303.GB9038@one.firstfloor.org> (raw)
In-Reply-To: <20080808132953.GB3840@redhat.com>
> Are you suggesting that kdump should be put onto panic_notifier_list, in
> such a way so that it runs last?
The point was that kernel debuggers have an at least as legitimate
need as kdump to run early on panic as kdump. In particularly they
should run before kdump because kdump can be triggered from
the debugger.
But for modular kernel debuggers the hook would need to be exported,
so in theory everyone could use it. In theory code review should
catch that. Another alternative would be to readd the old namespaces
patches I posted some time ago, this allowed to export symbols only
to specific modules (but that would be also unfortunate for out of tree
debuggers)
Since we have nearly all other needed hooks for kernel debuggers
anyways it doesn't really make sense to stop at panic. So this
earlier requirements should be relaxed.
Perhaps code review can solve the problem?
-Andi
next prev parent reply other threads:[~2008-08-08 18:02 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 17:22 jmerkey
[not found] ` <17494.166.70.238.46.1217784156.squirrel@webmail.wolfmountaingroup.com >
2008-08-03 19:36 ` jmerkey
2008-08-03 20:00 ` Rene Herman
2008-08-04 0:14 ` Josh Boyer
2008-08-04 2:19 ` jmerkey
2008-08-04 13:41 ` Stefan Richter
2008-08-04 14:33 ` jmerkey
2008-08-05 9:41 ` Geert Uytterhoeven
2008-08-05 15:02 ` jmerkey
2008-08-05 15:33 ` Nick Piggin
2008-08-05 15:19 ` jmerkey
2008-08-05 15:45 ` Nick Piggin
2008-08-05 15:32 ` jmerkey
2008-08-05 16:38 ` Nick Piggin
2008-08-05 16:45 ` jmerkey
2008-08-06 19:47 ` Rene Herman
2008-08-05 16:04 ` Chris Friesen
2008-08-05 16:39 ` jmerkey
2008-08-07 20:43 ` Daniel Barkalow
2008-08-07 21:02 ` jmerkey
2008-08-07 21:04 ` jmerkey
2008-08-05 17:21 ` Paul Mundt
2008-08-05 17:10 ` jmerkey
2008-08-06 3:08 ` Andi Kleen
2008-08-06 5:50 ` Nick Piggin
2008-08-07 17:45 ` Christoph Lameter
2008-08-07 17:53 ` jmerkey
2008-08-07 18:08 ` Stefan Richter
2008-08-07 19:10 ` Christoph Lameter
2008-08-07 19:47 ` Jay Lan
2008-08-07 19:34 ` jmerkey
2008-08-08 1:26 ` Vivek Goyal
2008-08-07 20:06 ` Andi Kleen
2008-08-07 20:07 ` Bernhard Walle
2008-08-07 20:09 ` Andi Kleen
2008-08-07 20:11 ` Bernhard Walle
2008-08-07 22:28 ` Keith Owens
2008-08-08 1:15 ` Vivek Goyal
2008-08-08 2:29 ` Andi Kleen
2008-08-08 12:08 ` Cliff Wickman
2008-08-08 12:20 ` Andi Kleen
2008-08-08 13:19 ` jmerkey
2008-08-08 15:06 ` Cliff Wickman
2008-08-08 13:29 ` Vivek Goyal
2008-08-08 14:50 ` Cliff Wickman
2008-08-08 16:57 ` Jay Lan
2008-08-11 12:56 ` Vivek Goyal
2008-08-08 18:03 ` Andi Kleen [this message]
2008-08-11 13:02 ` Vivek Goyal
2008-08-11 13:11 ` jmerkey
2008-08-11 13:50 ` Andi Kleen
2008-08-11 16:16 ` jmerkey
2008-08-18 9:12 ` Takenori Nagano
2008-08-08 8:40 ` Nick Piggin
2008-08-06 13:11 ` Bill Davidsen
2008-08-06 13:37 ` Stefan Richter
2008-08-06 13:54 ` Olivier Galibert
2008-08-06 13:45 ` jmerkey
2008-08-06 14:16 ` Nick Piggin
2008-08-06 17:21 ` Jason Wessel
2008-08-06 18:57 ` Andi Kleen
2008-08-07 12:45 ` jmerkey
2008-08-07 15:17 ` Peter Zijlstra
2008-08-07 16:07 ` Andi Kleen
2008-08-07 15:52 ` jmerkey
2008-08-07 17:04 ` Stefan Richter
2008-08-08 0:28 ` Stefan Richter
2008-08-11 10:36 ` jidong xiao
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=20080808180303.GB9038@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=bwalle@suse.de \
--cc=cl@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=jlan@sgi.com \
--cc=jmerkey@wolfmountaingroup.com \
--cc=jwboyer@gmail.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=stefanr@s5r6.in-berlin.de \
--cc=t-nagano@ah.jp.nec.com \
--cc=vgoyal@redhat.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®