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 a8e75ddc0dfb72a0857bbd3e3a789ed2b5a8a110..722836eada7a283fa065aa38def74156411d9ba4 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -16,14 +16,26 @@ The % symbol marks who is interested in the realisation of the item.<br>
 <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) 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>
@@ -46,12 +58,18 @@ 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) Change the byte pair "facility, event" id for a short combining the
+informatinon.<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) 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>
@@ -74,12 +92,14 @@ PPC64<BR>
 alpha<BR>
 user-mode Linux<BR>
 Xen<BR>
-# IBM
+# 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>
 <br>
 <br>
 <br>