From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: Building a tracing userspace tool in the kernel tree
Date: Thu, 9 Oct 2008 12:46:02 -0700 [thread overview]
Message-ID: <20081009124602.21a9b463.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081009191626.GA29344@Krystal>
On Thu, 9 Oct 2008 15:16:26 -0400
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> 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 ?
>
Sam's git://git.kernel.org/pub/scm/linux/kernel/git/sam/test.git#master
tree contains a tests/ directory in which various userspace things are
compiled. I'd suggest you build on top of that.
Sam, this tells us that what you have there is insufficiently general.
Mathieu's tracing thing isn't a "test", but it's userspace. We should
have
./userspace/tests/
./userspace/ltt/
no?
next prev parent reply other threads:[~2008-10-09 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:16 Building a tracing userspace tool in the kernel tree Mathieu Desnoyers
2008-10-09 19:46 ` Andrew Morton [this message]
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=20081009124602.21a9b463.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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