From: "H. Peter Anvin" <hpa@zytor.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
ksummit-2008-discuss@lists.linux-foundation.org,
Roland McGrath <roland@redhat.com>,
systemtap@sources.redhat.com
Subject: Re: [Ksummit-2008-discuss] Potential Systemtap topics for the Kernel Summit
Date: Thu, 03 Jul 2008 01:02:00 -0000 [thread overview]
Message-ID: <486C2504.6050608@zytor.com> (raw)
In-Reply-To: <486C20CA.4010503@redhat.com>
Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stephen Hemminger wrote:
>> On a related topic. Why not figure out a way to embed the tapsets
>> into the kernel source (a.l.a Docbook)?
>
> Sure, why not. The only problem is to come up with a notation which
> isn't too invasive. Frank's example showed one problem tapsets are
> supposed to solve: make parameters available under a name which doesn't
> change. Another goal for them is to make commonly used expressions
> derived from the state when entering the function available (e.g., inode
> belonging to a file descriptor).
>
> This kind of information might need a single line for each convenience
> variable defined in the tapset. So, it should be manageable.
>
They wouldn't even have to be embedded in the C code directly (unless
that makes them easier to write by being in situ), but even just having
them as separate files in the kernel tarball should make keeping them in
sync easier.
-hpa
next prev parent reply other threads:[~2008-07-03 1:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 13:57 DTrace Frank Ch. Eigler
2008-06-30 19:00 ` [Ksummit-2008-discuss] DTrace Grant Grundler
2008-06-30 19:40 ` Theodore Tso
2008-06-30 20:00 ` Frank Ch. Eigler
2008-06-30 20:19 ` Theodore Tso
2008-06-30 21:12 ` Arnaldo Carvalho de Melo
2008-06-30 23:02 ` David Miller
2008-06-30 21:13 ` James Bottomley
2008-06-30 22:10 ` Frank Ch. Eigler
2008-07-01 2:42 ` Theodore Tso
2008-07-01 7:08 ` Roland McGrath
2008-07-01 10:15 ` Theodore Tso
2008-07-01 11:04 ` Sam Ravnborg
2008-07-01 12:13 ` Theodore Tso
2008-07-02 20:27 ` Sam Ravnborg
2008-07-01 20:06 ` Roland McGrath
2008-07-01 23:13 ` Theodore Tso
2008-07-02 2:23 ` Frank Ch. Eigler
2008-07-02 19:27 ` Frank Ch. Eigler
2008-07-02 21:40 ` Potential Systemtap topics for the Kernel Summit Theodore Tso
2008-07-02 21:51 ` [Ksummit-2008-discuss] " Jonathan Corbet
2008-07-02 23:41 ` Arnaldo Carvalho de Melo
2008-07-02 22:38 ` Masami Hiramatsu
2008-07-02 22:54 ` [Ksummit-2008-discuss] " Stephen Hemminger
2008-07-03 0:44 ` Ulrich Drepper
2008-07-03 1:02 ` H. Peter Anvin [this message]
2008-07-03 1:50 ` Theodore Tso
2008-07-03 1:51 ` Ulrich Drepper
2008-07-02 20:08 ` [Ksummit-2008-discuss] DTrace Joel Becker
2008-07-02 20:17 ` J. Bruce Fields
2008-07-02 20:41 ` Frank Ch. Eigler
2008-07-02 21:19 ` H. Peter Anvin
2008-07-02 21:30 ` Theodore Tso
2008-07-02 21:46 ` J. Bruce Fields
2008-07-05 9:46 ` Peter Zijlstra
2008-07-05 10:07 ` Christoph Hellwig
2008-07-05 12:12 ` Frank Ch. Eigler
2008-07-05 18:08 ` Christoph Hellwig
2008-07-05 13:50 ` James Bottomley
2008-07-05 18:08 ` Christoph Hellwig
2008-07-05 18:05 ` K.Prasad
2008-07-07 14:36 ` Christoph Hellwig
2008-07-07 17:44 ` K.Prasad
2008-07-05 12:34 ` Theodore Tso
2008-07-01 5:29 ` Ananth N Mavinakayanahalli
2008-06-30 19:59 ` James Bottomley
2008-06-30 23:52 ` Masami Hiramatsu
2008-07-08 23:32 ` Eric W. Biederman
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=486C2504.6050608@zytor.com \
--to=hpa@zytor.com \
--cc=drepper@redhat.com \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--cc=roland@redhat.com \
--cc=shemminger@vyatta.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).