From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: next steps
Date: Mon, 26 Sep 2005 21:34:00 -0000 [thread overview]
Message-ID: <20050926213411.GA9468@rx8.austin.ibm.com> (raw)
In-Reply-To: <20050926153538.GA27733@redhat.com>
Frank Ch. Eigler <fche@redhat.com> [050926]:
> Hi -
>
> On Mon, Sep 26, 2005 at 10:11:01AM -0500, Jose R. Santos wrote:
>
> > [...] one of the requirements that the tool need is that for every
> > probe inserted, the cpu, pid, tid and a time-stamp (jiffies?) be
> > returned as well as some additional information that would be probe
> > specific.
>
> function ln /* labeled number */ (name, value) {
> print (name . "=" . string(value) . " ")
> }
> function trace_common_stuff () {
> ln ("cpu", cpu()) # cpu() to go into context tapset
This would need to look something like this:
function cpu:long () %{
if (unlikely(in_interrupt()))
THIS->__retvalue = 0;
else
THIS->__retvalue = task_cpu(current);
%}
right? Seems to be working on my 4-way system.
> ln ("pid", pid())
> ln ("jiffies", jiffies())) # jiffies() to go into in timestamp tapset
Just notice the availability of gettimeofday_(us/ms/s) on the
timestamp tapset so I don't think jiffies are needed. Either
way, it should be quick and painless to implement.
Thanks again.
-JRS
next prev parent reply other threads:[~2005-09-26 21:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 15:50 Frank Ch. Eigler
2005-09-21 15:46 ` Richard J Moore
2005-09-21 20:56 ` Frank Ch. Eigler
2005-09-21 23:33 ` Richard J Moore
2005-09-29 13:00 ` Masami Hiramatsu
2005-09-21 21:24 ` Martin Hunt
2005-09-21 23:58 ` Frank Ch. Eigler
2005-09-26 15:12 ` Jose R. Santos
2005-09-26 15:36 ` Frank Ch. Eigler
2005-09-26 16:26 ` Jose R. Santos
2005-09-26 16:56 ` Frank Ch. Eigler
2005-09-26 21:34 ` Jose R. Santos [this message]
2005-09-26 22:13 ` Frank Ch. Eigler
2005-09-27 15:30 ` Jose R. Santos
2005-09-26 17:44 ` thoughts Mathieu Desnoyers
2005-09-26 18:19 ` thoughts [re LTT] Frank Ch. Eigler
2005-09-26 18:30 ` Mathieu Desnoyers
2005-09-26 19:45 ` Karim Yaghmour
2005-09-29 16:44 ` thoughts Jose R. Santos
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=20050926213411.GA9468@rx8.austin.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).