From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca
Cc: Jan Blunck <jblunck@suse.de>, Martin Bligh <mbligh@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Zhaolei <zhaolei@cn.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, systemtap@sources.redhat.com
Subject: Updated TODO list before releasing LTTng buffering to LKML
Date: Tue, 28 Oct 2008 11:21:43 -0400 [thread overview]
Message-ID: <20081028152143.GD1136@Krystal> (raw)
Hi everyone,
Thanks for the steady work those past weeks. We are close to a
releasable result. I have been delighted to see people from Fujitsu
helping on various items in the past weeks. Thanks to all those who
report issues and/or provide patches.
Here is an updated Todo list before posting LTTng-buffering to LKML
Timestamping :
- Use kernel/time/tsc-sync.c in MIPS to detect unsync TSCs.
- Tweak kernel/time/tsc-sync.c so it supports sync detection between two
CPUs so it can be used to replace arch/x86/kernel/tsc_sync.c
- I plan to leave the current cache-line bouncing time source for CPUs
which have unsynched TSC, but to printk a warning telling the user to
disabled freq. scaling and halt in idle to make sure the clocks are
synchronized if he expects precise timestamping and good scalability
to large number of nodes. Let's keep room for improvement on this
aspect for later.
Markers :
- Tie the markers to event IDs and buffer name. That will permit to
simplify a lot of stuff currently in ltt-marker-control.ko. It will
also remove the need for a global event ID assignation, making it
per-buffer (in LTTng terminology : per-channel).
(will be done by myself soon)
- move ltt/ltt-marker-control.c /proc interface to debugfs
I think we should integrate its directory tree to the new LTTng tracer
debugfs API like this :
/debugfs/ltt/events/buffer_name/marker_name/
where we find files like :
state
write : 1/0 (on/off)
read : 1/0 (on/off)
format
read : marker format string
(being done by Fujistsu)
LTTng tracer :
- Rip apart ltt/ltt-core.c and put it in ltt/ltt-tracer.c. This
"builtin" part of LTTng can now sit in a module without any problem.
This can be done because we have the markers to abstract all
interactions with the tracer.
(will be done by myself soon)
- switch ltt-control.ko (currently over netlink) to debugfs
(being done by Fujistsu)
- Create a ltt-ascii.ko kernel module which merge-sorts the buffers and exports
them to userspace through a debugfs file.
(will be done by Fujistu)
- merge a simplified lttv in lttng
(will be done by myself)
As always, feel free to indicate if you are willing to help on any of
these items. If you need some pointers to the current state of work for
a particular item, just ask and I'll give you the pointer to the patch
within the -lttng git tree.
Thanks,
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2008-10-28 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081028152143.GD1136@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=jblunck@suse.de \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.