From: guijianfeng@cn.fujitsu.com (Gui Jianfeng)
Subject: [ltt-dev] move marker-control file into debugfs
Date: Mon, 12 Jan 2009 09:50:45 +0800 [thread overview]
Message-ID: <496AA1F5.1070106@cn.fujitsu.com> (raw)
In-Reply-To: <20090112014503.GB23423@Krystal>
Mathieu Desnoyers wrote:
> * Gui Jianfeng (guijianfeng at cn.fujitsu.com) wrote:
>> Hi Mathieu,
>>
>> I'd like to move "/proc/ltt" into debugfs. How do
>> you think of that? If you don't object, i'll post
>> a patch later, and update ltt-arm and other relative
>> tools.
>>
>
> Yes, this should be done. Please have a look at the discussion I had
> with Zhaolei on this. It was on the ltt-dev ML.
>
> Basically, the idea is to change the semantics a bit. The following
> directory tree would be great :
>
> /mnt/debugfs/ltt/markers/
> <channel_names>/
> <marker_names>/
>
> And within each individual <marker_names>/ directory, we would have
> those files :
>
> enabled (write, takes Y, y, 1 or N, n, 0. See ltt-trace-control.c.)
> (read, prints 1 or 0)
>
> We may want to remove the ability to connect markers to specific probes.
> Markers would always be only connected to the default serializer.
> Markers using ltt-type-serializer does not use the probe pointer anyway.
>
> We will probably want to let the
> kernel/marker.c:add_marker()/remove_marker() code call into the debugfs
> interface code to update the directory tree accordingly.
Thanks for your comments, i'll see what i can do.
>
> Regards,
>
> Mathieu
>
>
>> --
>> Regards
>> Gui Jianfeng
>>
>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>
>
--
Regards
Gui Jianfeng
next prev parent reply other threads:[~2009-01-12 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 1:20 Gui Jianfeng
2009-01-12 1:45 ` Mathieu Desnoyers
2009-01-12 1:50 ` Gui Jianfeng [this message]
2009-01-22 9:56 ` Gui Jianfeng
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=496AA1F5.1070106@cn.fujitsu.com \
--to=guijianfeng@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