(10): lowest priority<br>
<br>
<br>
-Dependencies are written between parenthesis ( ).<br>
+Dependencies are written between brackets [ ].<br>
The # symbol marks who is currently working on the item.<br>
The % symbol marks who is interested in the realisation of the item.<br>
<br>
<big>LTTV Roadmap<small><br>
<br>
* TODO<br>
-(1) Port LTTV to genevent-new parser.<br>
- # <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>>">Mathieu Desnoyers</A><br>
-(2) Fix bug with enums in lttv : make them use the value associated.<br>
-(4) create a event rate graphical view : Will be useful in conjonction with the
+(2) state.c : add Softirq execution mode.<br>
+(3) Make LTTV aware of type formats defined in the XML file.<br>
+(3) Use a per architecture enumeration for traps.<br>
+(3) Integrate Kernel State Dump information.<br>
+(4) create a event rate graphical view : Will be useful in conjunction with the
filter.<br>
# <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
-(6) migrate align to lttv parser.<br>
-(7) create an analysis of function time (like a precise gprof)<br>
+(4) create a graphical per cpu activity view.<br>
+(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
+(5) Event sequence detector (inspired from regular expressions).<br>
+(7) create an analysis of function time (like a precise gprof).<br>
-> with gcc -f inline-functions<br>
+(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss, page faults, interrupts...).<br>
(10) Add cancel button to LTTV filter GUI window.
<br>
<br>
<big>LTT Next Generation Roadmap<small><br>
<br>
* TODO<br>
-(1) Use 2.6.14 RelayFS control files.<br>
-(1) port LTTng to 2.6.14 kernel. (depends on genevent rewrite)<br>
(2) add efficient and secure user space tracing. (1 month)<br>
(3) integrate LTTng State Dump : missing irq and process state.<br>
# <A HREF="mailto:Jean-Hugues Deschenes <jean-hugues.deschenes@polymtl.ca>">Jean-Hugues Deschenes</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) Create the heartbeat timer LTTng module. Make sure that heartbeat events
+never hit the facility channel. Use the complete 64 bits TSC for the facility
+channel in every case. That's because this channel must never be overwritten
+even in "flight recorder" mode.<br>
(5) Integrate LTTng and lttd with LKCD.<br>
(7) add gcc -finstrument-functions instrumentation<br>
-(3) port LTTng to : (depends on 2.6.14 port)<br>
+(7) Integrate periodical dump of perfctr hardware counters.<br>
+(8) Integrate periodical dump of SystemTAP computed information.<br>
+(8) Integrate SystemTAP logging with LTTng.<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.10<BR>
+%Wind River for 2.6.14<BR>
PPC<BR>
PPC64<BR>
-%Wind River for 2.6.10<BR>
+%Wind River for 2.6.14<BR>
alpha<BR>
user-mode Linux<BR>
Xen<BR>
MIPS<BR>
MIPS64<BR>
-%Wind River for 2.6.10<BR>
+%Wind River for 2.6.14<BR>
ARM<BR>
S/390<BR>
<br>
and wakeup (causes a deadlock). -> Modify printk so it uses LTTng tracer!<br>
Export channels via network sockets instead of writing them to disk.<br>
Export buffers with time constraint for "live" visualisation. Use
-ltt_force_switch periodically from a timer to insure slow channels does not
+ltt_force_switch periodically from a timer to insure slow channels do not
interfere with viewing.<br>
<br>
* Need to be discussed<br>
+Use 2.6.14 RelayFS control files.<br>
Drop ltt-module-register and ltt-module-unregister, use exported variables.<br>
drop ltt_filter_control, use functions pointers instead.<br>
Merge facilities headers into one big header.<br>
projects / lttv.git / blobdiff