<big>LTTV Roadmap<small><br>
<br>
* TODO<br>
-(2) Add support for "stop" button in event list. (disabling event request
-scheduler)<br>
(2) Finish pre-computing of states to a file.<br>
(3) Add cluster support.<br>
# <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
(3) Make LTTV aware of type formats (visual separators) defined in the XML
file.<br>
(3) Use a per architecture enumeration for traps.<br>
+(3) Change the byte pair "facility, event" id for a short combining the
+informatinon.<br>
(4) Statistics per time window.<br>
(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.<br>
+(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
+cpus > 0.<br>
(4) Add event specific fields support to filter.<br>
(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
(4) create a graphical per cpu activity view.<br>
+(4) Filter by target process.<br>
+(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
(5) Add Python scripting hooks.<br>
(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
(5) Automatically detect traces with too much processes and disable faulty operations.<br>
view into a view of the evolution of a user definable event field.<br>
<br>
* TO FIX<br>
-(10) Event filter : event.time does not work.<br>
+(4) Fix scroll backward in detailed event list (introduced with "stop"
+functionnality.<br>
(10) Add cancel button to LTTV filter GUI window.<br>
(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
<big>LTT Next Generation Roadmap<small><br>
<br>
* TODO<br>
+(3) Find a way to make logging know when it causes a minor page fault
+recursively (without ignoring silently all nested events).<br>
+(3) Have various subbuffer sizes for high and low rate channels.<br>
+(3) Change the byte pair "facility, event" id for a short combining the
+informatinon.<br>
+(3) Add sysenter instrumentation on x86. Verify x86_64.<br>
+(3) #IBM Fix ppc64 syscall time accounting. Maybe caused by a missing syscall
+return instrumentation ?<br>
+(3) Process and kernel stack dump for x86_64, for native and compat.<br>
(4) Add Xen support.<br>
# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
# <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
(4) efficient dynamic event filtering while recording trace.<br>
% Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
(4) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.<br>
+(4) In flight recorder mode, have the low traffic channels saved as normal
+tracefiles and high traffic channels being flight recorder.<br>
+(4) Try to use my own non LOCK prefixed version of atomic operations : we are
+using per-CPU variables, so it should make it possible.<br>
(4) integrate NPTL instrumentation (see
<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
(5) Support CPUs with scalable frequency.<br>
* TODO (low priority)<br>
enhance RPM packages for lttng kernel<br>
Integrate header generation (genevent) in kernel build system.<br>
-Find a different way to printk from instrumentation : forbidden from schedule
-and wakeup (causes a deadlock). -> Modify printk so it uses LTTng tracer!<br>
Export channels via network sockets instead of writing them to disk.<br>
Export buffers with time constraint for "live" visualisation. Use
ltt_force_switch periodically from a timer to insure slow channels do not
projects / lttv.git / blobdiff