update roadmap

[lttv.git] / ltt / branches / poly / doc / developer / lttng-lttv-roadmap.html

diff --git a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
index a310a5a776c16731a4977fa2a15f783d14652d11..37915f9a2f0b9fcc9893bac582c58dcfdd417ca9 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -33,6 +33,7 @@ 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>
@@ -43,6 +44,8 @@ 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.<br>
 <br>
 * TO FIX<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
@@ -57,14 +60,18 @@ of process 0.<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>
 (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