update compat

[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 a669b0db600fa7c5b6ea3a94a759a8157a5932be..243d0c7317a3e5d9201f2241b8dff42151b9364c 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -34,6 +34,7 @@ cpus > 0.<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) Compensate for time spent in probes in LTTV analysis.<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>
@@ -44,8 +45,6 @@ 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
@@ -58,6 +57,7 @@ of process 0.<br>
 <big>LTT Next Generation Roadmap<small><br>
 <br>
 * TODO<br>
+(1) Announce LTTng patches on LKML.<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>
@@ -79,6 +79,9 @@ tracefiles and high traffic channels being flight recorder.<br>
 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>
+(4) Probe calibration kernel module.<br>
+(5) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
+(5) Move to DebugFS for channel files.<br>
 (5) Support CPUs with scalable frequency.<br>
 (5) Integrate LTTng and lttd with LKCD.<br>
 (7) Integrate periodical dump of perfctr hardware counters.<br>