From: andrew.mcdermott@windriver.com (Andrew McDermott)
Subject: [ltt-dev] TODO list before releasing LTTng-buffering to LKML
Date: Tue, 14 Oct 2008 10:17:29 +0100 [thread overview]
Message-ID: <v4ej2jtu1i.fsf@swi-aim.swindon.wrsec.fr> (raw)
In-Reply-To: <48F45D5A.6060802@cn.fujitsu.com> (Lai Jiangshan's message of "Tue, 14 Oct 2008 16:50:34 +0800")
Lai Jiangshan <laijs at cn.fujitsu.com> writes:
> * Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
>> Hi!
>>
>> Just to keep you posted on the current development, this is what is left
>> on my roadmap before I post a minimal LTTng (only the timestamping,
>> event ID management and buffering) to LKML :
>>
>> Todo list before posting LTTng-buffering to LKML
>
> [...]
>
>> - switch ltt-control.ko (currently over netlink) to debugfs
>> - switch marker list (and marker activation (currently in /proc/ltt) to debugfs
>> Marker directory. One file per marker.
>> - Create a ltt-ascii.ko kernel module which merge-sorts the buffers and exports
>> them to userspace through a debugfs file.
>>
>
> Hi, Mathieu,
>
> We are interested with the above TODOs, and we are planning to implement them.
>
> Thanks, Lai
>
>> If some of you are interested to work on any of these, you are welcome.
>> I'll be glad to post more details about these items upon request.
Do you plan on doing this work in the context of 2.6.27? I was trying
to understand where the switch to debugfs for ltt-control and the marker
list was going to take place.
Thanks,
Andy.
>>
>> Mathieu
>>
>
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
--
andy
prev parent reply other threads:[~2008-10-14 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 1:02 Mathieu Desnoyers
2008-10-09 2:21 ` Mathieu Desnoyers
2008-10-24 20:38 ` Mathieu Desnoyers
2008-10-27 3:10 ` Zhaolei
2008-10-14 8:50 ` Lai Jiangshan
2008-10-14 9:17 ` Andrew McDermott [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=v4ej2jtu1i.fsf@swi-aim.swindon.wrsec.fr \
--to=andrew.mcdermott@windriver.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