temp debug remove

[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 37915f9a2f0b9fcc9893bac582c58dcfdd417ca9..36d4bcfa0096fb5bc81c7e5026563e5815b28a12 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,12 +57,9 @@ of process 0.<br>
 <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>
 (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>
@@ -76,6 +72,12 @@ 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>
+(4) Make page faults detect nested fault without nesting 4 times in the page
+fault handler.<br>
+(4) #IBM Test fix for ppc64 kernel 2.6.9 missing syscall return instrumentation.<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>
@@ -85,22 +87,10 @@ using per-CPU variables, so it should make it possible.<br>
 ltt-instrument-functions.<br>
 (9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
 (3) port LTTng to :<br>
-x86_64<BR>
-#Autodesk <A HREF="mailto:Francois L'Archeveque <fla@discreet.com>">Francois
-L'Archeveque</A> for 2.6.9 RedHat Enterprise (patch available in contrib, still
-has to be ported to 2.6.14, thanks!)<BR>
-# Wind River for 2.6.14<BR>
-PPC<BR>
-PPC64<BR>
-# Wind River for 2.6.14<BR>
 alpha<BR>
 user-mode Linux<BR>
 Xen<BR>
 # IBM<BR>
-MIPS<BR>
-MIPS64<BR>
-% Wind River for 2.6.14<BR>
-# Tim Bird <A HREF="mailto:tim.bird@as.sony.com">Tim Bird</A><br>
 S/390<BR>
 RTLinux<BR>
 % Wind River for 2.6.14<BR>