From: fche@redhat.com (Frank Ch. Eigler)
To: Li Guanglei <guanglei@cn.ibm.com>
Cc: <systemtap@sourceware.org>
Subject: Re: Customization of LKET
Date: Thu, 08 Jun 2006 16:04:00 -0000 [thread overview]
Message-ID: <y0mverbsklx.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <44863368.9060805@cn.ibm.com>
Li Guanglei <guanglei@cn.ibm.com> writes:
> [...]
> I though of another way of allowing the user add arbitrary extra trace
> data using just printf. [...]
> register_user_event(GROUP_NETDEV, HOOKID_NETDEV_RECEIVE,
> "STRING:INT8:INT16", "sample string:sample id1:sample id2")
> [...]
Yes, this could work, though the script author will have to make the
register declarative call match his later actual usage.
It is worth realizing though that this is just the kind of metadata
that the "compiled" binary tracing we proposed could provide
automatically.
- FChE
prev parent reply other threads:[~2006-06-08 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 14:38 Li Guanglei
2006-05-31 7:49 ` Li Guanglei
2006-06-01 23:22 ` Frank Ch. Eigler
2006-06-02 3:19 ` Li Guanglei
2006-06-02 11:31 ` Frank Ch. Eigler
2006-06-07 2:00 ` Li Guanglei
2006-06-08 16:04 ` Frank Ch. Eigler [this message]
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=y0mverbsklx.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=guanglei@cn.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).