All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org,
	utrace-devel <utrace-devel@redhat.com>,
	Roland McGrath <roland@redhat.com>,
	Jim Keniston <jkenisto@us.ibm.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure.
Date: Mon, 30 Nov 2009 10:29:10 -0500	[thread overview]
Message-ID: <20091130152910.GB10331@redhat.com> (raw)
In-Reply-To: <20091130151650.GA24316@elte.hu>

On Mon, Nov 30, 2009 at 04:16:50PM +0100, Ingo Molnar wrote:
> [...]
> kgdb exists here and today in the kernel and you cannot just build a 
> facility that doesnt replace it and doesnt integrate well with it.

Surely you don't mean that: every non-kgdb facility in the kernel
meets that definition, even all debugging-related facilities such as
perf and ftrace.


> So if a unified user/kernel model for debugging is a 'long term'
> feature in your view then perhaps this framework (which introduces
> _extensive_ hooks all around the kernel) is not designed/approached
> in the right way and should not be merged in this form.

Which "this framework" are you talking about?  Please clarify what
exactly you're trying to say.


- FChE

  reply	other threads:[~2009-11-30 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 12:03 [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure Srikar Dronamraju
2009-11-30 12:09 ` Peter Zijlstra
2009-11-30 12:32   ` Srikar Dronamraju
2009-11-30 12:41     ` Peter Zijlstra
2009-11-30 13:19       ` Srikar Dronamraju
2009-11-30 13:37         ` Peter Zijlstra
2009-11-30 14:05           ` Srikar Dronamraju
2009-11-30 15:03           ` Frank Ch. Eigler
2009-11-30 15:11             ` Peter Zijlstra
2009-11-30 15:16             ` Ingo Molnar
2009-11-30 15:29               ` Frank Ch. Eigler [this message]
2009-12-01 16:11                 ` Ingo Molnar
2009-12-01 17:00                   ` Frank Ch. Eigler
2009-12-01 17:09                     ` Ingo Molnar
2009-12-01 17:45                       ` Frank Ch. Eigler
2009-12-01 21:15                         ` Ingo Molnar
2009-12-08 21:58                           ` Frank Ch. Eigler
2009-12-10  7:41                             ` Ingo Molnar
2009-12-10 15:08                               ` Frank Ch. Eigler
2009-12-10 18:16                                 ` Ingo Molnar
2009-12-11  1:27                                   ` Frank Ch. Eigler

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=20091130152910.GB10331@redhat.com \
    --to=fche@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=roland@redhat.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=utrace-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.