From: Ingo Molnar <mingo@elte.hu>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
utrace-devel <utrace-devel@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure.
Date: Thu, 10 Dec 2009 19:16:38 +0100 [thread overview]
Message-ID: <20091210181638.GA17986@elte.hu> (raw)
In-Reply-To: <y0mhbryamt2.fsf@fche.csb>
* Frank Ch. Eigler <fche@redhat.com> wrote:
>
> Ingo Molnar <mingo@elte.hu> writes:
>
> > [...] Since the speed of development in this area is truly glacial
> > at the moment and the practical advantages that i can experience
> > personally (directly as a Linux user and indirectly as a maintainer)
> > are miniscule so far, caution is warranted IMO. [...]
>
> If the "caution" you suggest is operationally equivalent to
> discouraging even miniscule improvements, is it any wonder that
> progress is glacial?
I think you might be mixing up cause and causation ;-)
> The gdbstub prototype was constructed for two reasons: to demonstrate
> utrace usage now, and in the future to be incrementally useful (over
> ptrace, by moving into fast kernel-space operations like
> multithreading control, gdb-tracepoint support, other stuff). #1 is
> about done. With respect to #2, we can certainly commit to ongoing
> work on improvements, provided the community shows interest and
> goodwill.
What i'd like to see is measurable benefits to users, developers and
maintainers. I'd like to see the same for SystemTap too btw.
Ingo
next prev parent reply other threads:[~2009-12-10 18:17 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
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 [this message]
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=20091210181638.GA17986@elte.hu \
--to=mingo@elte.hu \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox