From: Dave Nomura <dcnltc@us.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org, Maynard Johnson <mpjohn@us.ibm.com>
Subject: Re: user instruction tracing patch?
Date: Mon, 04 Feb 2008 16:58:00 -0000 [thread overview]
Message-ID: <47A74403.8070804@us.ibm.com> (raw)
In-Reply-To: <20071210175940.GB14686@redhat.com>
The Perfomance Inspector group, who currently host the ITRACE tool on,
are interested in exploring the use of Systemtap to build their ITRACE
tool on RedHat. In an effort to jump start them I am planning on
submitting my user instruction tracing patch to them and helping them
build an ITRACE RPM that does userspace level instruction tracing as
well as some other functionality that they are interested in. This does
not diminish our commitment to getting this functionality into
Systemtap, but is more of a temporary measure. In the long term I
envision the basic userspace instruction tracing functionality
integrated into Systemtap, and PI possibly building on this framework to
support some of the other features that they are interested in.
I should be able to start doing the Systemtap translator work as soon as
I finish up helping with the PI effort. Since I am a SystemTap
neophyte I am hoping to get some guidance from you, the Systemtap
community, and hopefully with local help from Jim Keniston.
Frank Ch. Eigler wrote:
> Hi -
>
>
>> So what do you think the next steps are to move forward on this issue?
>> Did you have some expectations on who would do this translator work?
>>
>
> We need that famous "someone" to do the work. Would you like to try
> it? It should not be much harder than (say) the timer.profile
> implementation.
>
>
>> From your discussion it sounded like some of these issues were more
>> general than just instruction tracing. Are there plans to do any of
>> that work?
>>
>
> Yes, some of them are underway.
>
> - FChE
>
--
Dave Nomura
LTC Linux Power Toolchain
next prev parent reply other threads:[~2008-02-04 16:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 17:58 Dave Nomura
2007-11-14 21:29 ` Frank Ch. Eigler
2007-11-14 21:59 ` Roland McGrath
2007-11-14 23:17 ` Frank Ch. Eigler
2007-11-14 23:39 ` Roland McGrath
2007-11-15 3:59 ` Frank Ch. Eigler
2007-11-16 0:04 ` Jim Keniston
2007-11-16 17:18 ` Frank Ch. Eigler
2007-11-16 18:36 ` Jim Keniston
2007-11-16 19:21 ` Frank Ch. Eigler
2007-11-16 20:20 ` Jim Keniston
2007-11-16 20:29 ` Roland McGrath
2007-11-16 20:38 ` Frank Ch. Eigler
2007-11-16 21:08 ` Jim Keniston
2007-11-16 21:25 ` Frank Ch. Eigler
2007-11-16 21:51 ` Jim Keniston
2007-11-16 22:23 ` Frank Ch. Eigler
2007-11-27 14:13 ` Dave Nomura
2007-11-27 15:14 ` Frank Ch. Eigler
2007-12-03 18:09 ` Dave Nomura
2007-12-10 18:00 ` Frank Ch. Eigler
2008-02-04 16:58 ` Dave Nomura [this message]
2008-03-10 18:49 ` Dave Nomura
2008-03-17 15:16 ` Frank Ch. Eigler
[not found] ` <47E157A8.3010508@us.ibm.com>
2008-03-19 18:42 ` 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=47A74403.8070804@us.ibm.com \
--to=dcnltc@us.ibm.com \
--cc=fche@redhat.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).