From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Building a tracing userspace tool in the kernel tree
Date: Thu, 9 Oct 2008 15:16:26 -0400 [thread overview]
Message-ID: <20081009191626.GA29344@Krystal> (raw)
Hi Sam,
At the kernel summit, people seemed to be interested to have the basic
userspace tools required to extract and pretty-print a trace available
within the kernel tree. Therefore, what I am trying to do is something
along the lines of
ltt/usr/
ltt/usr/tracectl/ (control tracing)
ltt/usr/tracesplice/ (splice buffers to disk)
ltt/usr/tracecat/ (merge sort and format the binary buffers into
human-readable text)
That would however require to create a Makefile which behaves a little
bit like what scripts/ is currently doing with hostprogs-y, only that
it's different in the sense that those tools are not required to build
the kernel and this could therefore become a more standard part of the
build process than what scripts/ is.
Is there some magic statements to put in Makefile and ltt/Makefile to
get this to build nicely with the rest of the tree ?
Thanks,
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2008-10-09 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:16 Mathieu Desnoyers [this message]
2008-10-09 19:46 ` Building a tracing userspace tool in the kernel tree Andrew Morton
2008-10-09 22:15 ` Peter Zijlstra
2008-10-09 22:35 ` Chris Friesen
2008-10-09 22:40 ` Peter Zijlstra
2008-10-09 23:11 ` Chris Friesen
2008-10-09 23:12 ` Mathieu Desnoyers
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=20081009191626.GA29344@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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