X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=ltt%2Fbranches%2Fpoly%2Fdoc%2Fdeveloper%2Flttng-lttv-roadmap.html;h=243d0c7317a3e5d9201f2241b8dff42151b9364c;hb=fd61f76041fad8334955b442f9c423ea910b2b3c;hp=8e4aa6e8bb8e282533e0974048c69751ce8a0300;hpb=b4b2bb060df6c679a962eed59f0e721a510d208c;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 8e4aa6e8..243d0c73 100644
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -33,6 +33,8 @@ 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) 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>
@@ -55,11 +57,16 @@ 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>
 (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>
@@ -72,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>