X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=ltt%2Fbranches%2Fpoly%2Fdoc%2Fdeveloper%2Flttng-lttv-roadmap.html;h=ecd29cf7b3205bbbe29767a04cfee3a01c7cddcc;hb=11df8cd57d94c108ec0d17a379d5cbc0662aec27;hp=1d9730228edc949678e24577f2d8096344b963d2;hpb=ac70a3eb13b7aee7f063a5ab9c41ca0cc590ff38;p=lttv.git

diff --git a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
index 1d973022..ecd29cf7 100644
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -16,7 +16,6 @@ The % symbol marks who is interested in the realisation of the item.<br>
 <big>LTTV Roadmap<small><br>
 <br>
 * TODO<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
@@ -37,6 +36,7 @@ cpus > 0.<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) Add GUI interface to take an hybrid trace.<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>
 (5) Event sequence detector (inspired from regular expressions).<br>
@@ -57,30 +57,25 @@ 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>
+(1) Move to DebugFS for channel files.<br>
+(2) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
+(2) Rethink facility logging code (genevent output).<br>
+(2) Post an updated LTTng version to LKML (2.6.18-rcX).<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>
 (4) Probe calibration kernel module.<br>
-(5) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
-(5) Move to DebugFS for channel files.<br>
+(4) Make page faults detect nested fault without nesting 4 times in the page
+fault handler.<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>