From: fche@redhat.com (Frank Ch. Eigler)
To: Dominique Toupin <dominique.toupin@ericsson.com>
Cc: <gdb@sourceware.org>, <systemtap@sourceware.org>
Subject: Re: Static/dynamic userspace/kernel trace
Date: Tue, 20 Apr 2010 17:28:00 -0000 [thread overview]
Message-ID: <y0mljcihw3d.fsf@fche.csb> (raw)
In-Reply-To: <D58A856745AB5A47B1448181D1A8BBFA01CB208AA0@EUSAACMS0701.eamcs.ericsson.se> (Dominique Toupin's message of "Mon, 19 Apr 2010 15:50:01 -0400")
Dominique Toupin <dominique.toupin@ericsson.com> writes:
> I agree that GDB could use a better ptrace.
Right. And since ptrace proper is needed as a backward compatibility
measure, the kernel will in turn need something to multiplex/arbitrate
between the different interfaces. So this is how we came to utrace
years ago.
> Regarding tracing, for me the main use case is to get the data out
> of the system very fast and with very low overhead [...]
Understood. That same approach underlies other tracing/performance
tools. For systemtap, this has been more of an asymptotic case:
something it can do too, with other tools providing some tough-to-beat
performance (and sometimes usability) benchmarks.
- FChE
next prev parent reply other threads:[~2010-04-20 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D58A856745AB5A47B1448181D1A8BBFA01CB20875C@EUSAACMS0701.eamcs.ericsson.se>
2010-04-19 14:14 ` Frank Ch. Eigler
2010-04-19 19:50 ` Dominique Toupin
2010-04-20 7:59 ` Mark Wielaard
2010-04-22 19:46 ` Dominique Toupin
2010-04-20 17:28 ` Frank Ch. Eigler [this message]
2010-04-20 14:01 ` Srikar Dronamraju
2010-04-20 18:06 ` Stan Shebs
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=y0mljcihw3d.fsf@fche.csb \
--to=fche@redhat.com \
--cc=dominique.toupin@ericsson.com \
--cc=gdb@sourceware.org \
--cc=systemtap@sourceware.org \
/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