[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48EE871A.2030302@nortel.com>
Date: Thu, 09 Oct 2008 16:35:06 -0600
From: "Chris Friesen" <cfriesen@...tel.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: Building a tracing userspace tool in the kernel tree
Peter Zijlstra wrote:
> On Thu, 2008-10-09 at 15:16 -0400, Mathieu Desnoyers 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)
>
>
> I'd rather have you provide that interface from the kernel much like
> ftrace does. So we can do:
>
> # cat /debug/tracing/lttng/trace
>
Do we really want to reserve memory in the kernel to store all the data?
Assuming not, do we really want to have to deal with filesystem
namespaces in the kernel when interpreting which file we want to log to?
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists