LTTV & LTTng roadmap

Here are the roadmaps for the LTTV and LTTng development. I use a priority indice for the TODO items :
(1) : very high priority
(10): lowest priority


Dependencies are written between brackets [ ].
The # symbol marks who is currently working on the item.
The % symbol marks who is interested in the realisation of the item.

LTTV Roadmap

* TODO
(1) Marker integration. Change the byte pair "facility, event" id for a short combining the informatinon.
# Mathieu Desnoyers
(3) Add cluster support.
# Eric Clement
(3) Make LTTV aware of type formats (visual separators) defined in the XML file.
# Gabriel Matni
(3) Use a per architecture enumeration for traps.
(4) Statistics per time window.
(4) Add Xen per physical CPU view.
(4) Add Xen per vcpu view.
(4) Disable plugins when threshold reached (i.e. too much process in control flow view). Draw, and, when the threshold is reached, stop drawing. The global statistics view can inhibit showing the per process stats.
(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for cpus > 0.
(4) Add event specific fields support to filter.
(4) Add a periodic event interval view. (useful to verify event periodicity)
(4) create a graphical per cpu activity view.
(4) Filter by target process.
(4) Compensate for time spent in probes in LTTV analysis.
(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]
(4) Add sort by process priority in the control flow view (must also instrument priority information of the processes).
% Airbus
(5) Add Python scripting hooks.
(5) Add GUI interface to take an hybrid trace.
(5) Flight recorder : start lttd automatically upon GUI trace control stop.
(5) Automatically detect traces with too much processes and disable faulty operations.
(5) Event sequence detector (inspired from regular expressions).
(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss, page faults, interrupts...). This will be a generalisation of the event rate view into a view of the evolution of a user definable event field.

* TO FIX
(10) Add cancel button to LTTV filter GUI window.
(10) Sometimes, in the control flow view, a process with 0 creation time is created in addition to the real process itself. Seems to be caused by end of process life.
(10) Statistics do not take in account the time spent in the mode present at the beginning of the trace. Example : real time spent in system call on behalf of process 0.


LTT Next Generation Roadmap

* TODO
(1) efficient dynamic event filtering while recording trace.
% Google
% Sensis Corp. Tim Bish
# Mathieu Desnoyers
- Partly implemented: per marker selection through /proc interface.
- Must still implement per active trace filtering.
(1) Add Xen support. (Trace buffer desallocation needs to be fixed)
# Mathieu Desnoyers
(1) Integrate SystemTAP logging with LTTng.
(4) instrument kernel bottom half irqsave, seqlocks, semaphores, mutexes, brlock.
(4) integrate NPTL instrumentation (see PTT).
(4) Probe calibration kernel module.
(4) Make page faults detect nested fault without nesting 4 times in the page fault handler.
(5) Support CPUs with scalable frequency.
(5) Add boot time tracing support.
(5) Integrate LTTng and lttd with LKCD.
(7) Integrate periodical dump of perfctr hardware counters.
(8) Integrate periodical dump of SystemTAP computed information.
(9) Add support for setjmp/longjmp and jump tables instrumentation to ltt-instrument-functions.
(9) Make ltt-usertrace-fast support internal heartbeat timer.
(3) port LTTng to :
alpha
user-mode Linux
Xen
# IBM
S/390
RTLinux
% Wind River for 2.6.14
sparc64
# Wind River
sh4



* TODO (low priority)
enhance RPM packages for lttng kernel
Integrate header generation (genevent) in kernel build system.
Export channels via network sockets instead of writing them to disk.
Export buffers with time constraint for "live" visualisation. Use ltt_force_switch periodically from a timer to insure slow channels do not interfere with viewing.
Have an optional round-robin mode to write information into multiple channels from the same source.

* Need to be discussed
Use 2.6.14 RelayFS control files.
Drop ltt-module-register and ltt-module-unregister, use exported variables.
drop ltt_filter_control, use functions pointers instead.
Merge facilities headers into one big header.
Change the name of XML files from XML to something else.
Remove ltt-base.c.

Mathieu Desnoyers