From: zhaolei@cn.fujitsu.com (Zhaolei)
Subject: [ltt-dev] TODO list before releasing LTTng-buffering to LKML]
Date: Fri, 17 Oct 2008 11:56:13 +0800 [thread overview]
Message-ID: <48F80CDD.2070205@cn.fujitsu.com> (raw)
Message-ID: <20081017035613.O3S67LZGcOYrqd6qhZjODyQMsK-IBVT60DEMw9keIOI@z> (raw)
In-Reply-To: <48F733E6.9010007@cn.fujitsu.com>
>> - 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.
>
Hi Mathieu,
I finished a simple ltt-control.ko based on debugfs.
With this module, we can control ltt by following command now:
Start trace1 channel:
echo "0 trace1" > /sys/kernel/debug/ltt_control/control
Stop trace1 channel:
echo "1 trace1" > /sys/kernel/debug/ltt_control/control
Create trace1 channel:
echo "2 trace1 relay 0 0 0 0 0 0 0" > /sys/kernel/debug/ltt_control/control
Destroy trace1 channel:
echo "3 trace1" > /sys/kernel/debug/ltt_control/control
I tested it on i386 linux 2.6.27 with lttng.
User-mode lttctl also needs some modification to support this kind of control,
but at first, I'd like to hear some advice on this module.
Thanks!
Zhaolei
> 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.
>>
>> Mathieu
>>
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Makefile
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20081017/6261648f/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ltt_control.c
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20081017/6261648f/attachment.txt>
next parent reply other threads:[~2008-10-17 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48F733E6.9010007@cn.fujitsu.com>
2008-10-17 3:56 ` Zhaolei [this message]
2008-10-17 3:56 ` Zhaolei
2008-10-17 3:56 ` Zhaolei
[not found] ` <20081017042045.GB5067@Krystal>
2008-10-17 6:31 ` Zhaolei
[not found] ` <20081017161429.GA5696@Krystal>
2008-10-20 3:03 ` Zhaolei
[not found] ` <20081020031634.GA14209@Krystal>
2008-10-27 3:47 ` [ltt-dev] [PATCH] Separate ltt_trace_create() into ltt_trace_create() and ltt_trace_alloc() Zhaolei
2008-10-28 14:25 ` Mathieu Desnoyers
2008-10-29 4:04 ` [ltt-dev] [PATCH] Separate ltt_trace_create() intoltt_trace_create() " Zhaolei
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=48F80CDD.2070205@cn.fujitsu.com \
--to=zhaolei@cn.fujitsu.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