public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	hch@infradead.org, pagg@oss.sgi.com, erikj@sgi.com, pj@sgi.com,
	matthltc@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] add task handling notifier
Date: Wed, 9 Jan 2008 10:03:44 +0000	[thread overview]
Message-ID: <20080109100344.GA7342@infradead.org> (raw)
In-Reply-To: <4784A751.76E4.0078.0@novell.com>

On Wed, Jan 09, 2008 at 09:52:01AM +0000, Jan Beulich wrote:
> Yes. And the unidentified feature is NLKD. But as with other notifiers (most
> notably the module unload one), all reasonable kernel debuggers should
> need them (or do explicit patching of the mentioned source files). As I
> explained before, I think that if kernel debuggers aren't allowed into the
> tree, they should at least be allowed to co-exist (since the argument of
> requiring in-tree users and submitting code for mainline inclusion is void
> if political/personal reasons exclude certain code from even being
> considered for inclusion).

We already have a kernel debugger in tree, xmon.  There's anotherone
hopefully getting in soon (kgdb), so they can do the right thing as the
other subsystems.

And as usual, we're not going to provide hooks for out of tree mess.


  reply	other threads:[~2008-01-09 10:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 13:11 [PATCH 0/4] add task handling notifier Jan Beulich
2007-12-20 22:25 ` Ingo Oeser
2007-12-21  7:36   ` Jan Beulich
2007-12-23 12:26 ` Christoph Hellwig
2007-12-25 22:05   ` Andrew Morton
2008-01-08 13:38     ` Jan Beulich
2008-01-08 22:14       ` Andrew Morton
2008-01-09  0:03         ` Paul Jackson
2008-01-09  0:31           ` Andrew Morton
2008-01-09  2:47         ` Matt Helsley
2008-01-09  3:22           ` Andrew Morton
2008-01-09  9:52         ` Jan Beulich
2008-01-09 10:03           ` Christoph Hellwig [this message]
2008-01-09  2:24   ` Matt Helsley
2008-01-09  3:27     ` Matthew Helsley

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=20080109100344.GA7342@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=erikj@sgi.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=pagg@oss.sgi.com \
    --cc=pj@sgi.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