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=a310a5a776c16731a4977fa2a15f783d14652d11;hpb=7485a6f8e714ad9bafdb5e8d590ea0c2c8557b5d;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 a310a5a7..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.
(4) Add event specific fields support to filter.
(4) Add a periodic event interval view. (useful to verify event periodicity)
(4) create a graphical per cpu activity view.
+(4) Filter by target process.
+(4) Compensate for time spent in probes in LTTV analysis.
(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]
(5) Add Python scripting hooks.
(5) Flight recorder : start lttd automatically upon GUI trace control stop.
@@ -55,20 +57,31 @@ of process 0.
LTT Next Generation Roadmap

* TODO
+(1) Announce LTTng patches on LKML.
(3) Find a way to make logging know when it causes a minor page fault recursively (without ignoring silently all nested events).
+(3) Have various subbuffer sizes for high and low rate channels.
(3) Change the byte pair "facility, event" id for a short combining the informatinon.
+(3) Add sysenter instrumentation on x86. Verify x86_64.
+(3) #IBM Fix ppc64 syscall time accounting. Maybe caused by a missing syscall +return instrumentation ?
+(3) Process and kernel stack dump for x86_64, for native and compat.
(4) Add Xen support.
# Mathieu Desnoyers
# Parisa Heidari
(4) efficient dynamic event filtering while recording trace.
% Sensis Corp. Tim Bish
(4) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.
+(4) In flight recorder mode, have the low traffic channels saved as normal +tracefiles and high traffic channels being flight recorder.
(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.
(4) integrate NPTL instrumentation (see PTT).
+(4) Probe calibration kernel module.
+(5) Discuss with RelayFS upstream to integrate LTTng modifications.
+(5) Move to DebugFS for channel files.
(5) Support CPUs with scalable frequency.
(5) Integrate LTTng and lttd with LKCD.
(7) Integrate periodical dump of perfctr hardware counters.