From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dave Nomura <dcnltc@us.ibm.com>
Cc: systemtap@sourceware.org, Maynard Johnson <mpjohn@us.ibm.com>
Subject: Re: proposed instruction trace support in SystemTap
Date: Wed, 29 Aug 2007 16:25:00 -0000 [thread overview]
Message-ID: <20070829160437.GA18075@redhat.com> (raw)
In-Reply-To: <46D590B7.3040808@us.ibm.com>
Hi -
On Wed, Aug 29, 2007 at 08:28:55AM -0700, Dave Nomura wrote:
> Would the performance of utrace be acceptable for doing instruction
> tracing?
Probably.
> It sounds like a lot of the signal overhead of ptrace is eliminated.
Yes.
> Would utrace only be useful for user-mode stepping,
Yes.
> or could it somehow handle the in-kernel case?
No.
- FChE
next prev parent reply other threads:[~2007-08-29 16:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 23:01 Dave Nomura
2007-07-05 19:37 ` Frank Ch. Eigler
2007-07-06 12:46 ` grundy
2007-07-06 14:59 ` Frank Ch. Eigler
2007-07-06 21:43 ` Maynard Johnson
2007-07-07 1:58 ` Frank Ch. Eigler
2007-07-10 15:47 ` Maynard Johnson
2007-07-10 14:12 ` Dave Nomura
2007-07-10 14:39 ` Frank Ch. Eigler
2007-07-10 20:57 ` Maynard Johnson
2007-07-10 22:45 ` Jim Keniston
2007-07-11 4:31 ` Ananth N Mavinakayanahalli
2007-08-20 0:34 ` Dave Nomura
2007-08-20 0:37 ` Roland McGrath
2007-08-25 11:34 ` Dave Nomura
2007-08-29 14:57 ` Frank Ch. Eigler
2007-08-30 5:43 ` kernel API for in-kernel single stepping Dave Nomura
2007-08-30 13:05 ` Paul Mackerras
2007-09-04 3:05 ` Frank Ch. Eigler
2007-09-05 5:02 ` Dave Nomura
2007-08-29 15:40 ` proposed instruction trace support in SystemTap Dave Nomura
2007-08-29 16:25 ` Frank Ch. Eigler [this message]
2007-09-06 2:57 ` using utrace for instruction tracing Dave Nomura
2007-09-06 14:05 ` Jim Keniston
2007-09-06 18:28 ` Dave Nomura
2007-08-23 22:10 ` proposed instruction trace support in SystemTap Dave Nomura
2007-07-06 21:39 ` Maynard Johnson
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=20070829160437.GA18075@redhat.com \
--to=fche@redhat.com \
--cc=dcnltc@us.ibm.com \
--cc=mpjohn@us.ibm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).