ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html

   1 <html>
   2 <body>
   3 <center><big><big>LTTV & LTTng roadmap<small><small></center>
   4 <br>
   5 <br>
   6 Here are the roadmaps for the LTTV and LTTng development. I use a priority indice
   7 for the TODO items :<br>
   8 (1) : very high priority<br>
   9 (10): lowest priority<br>
  10 <br>
  11 <br>
  12 Dependencies are written between brackets [ ].<br>
  13 The # symbol marks who is currently working on the item.<br>
  14 The % symbol marks who is interested in the realisation of the item.<br>
  15 <br>
  16 <big>LTTV Roadmap<small><br>
  17 <br>
  18 * TODO<br>
  19 (2) Finish pre-computing of states to a file.<br>
  20 (3) Add cluster support.<br>
  21         # <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
  22 (3) Make LTTV aware of type formats (visual separators) defined in the XML
  23 file.<br>
  24 (3) Use a per architecture enumeration for traps.<br>
  25 (3) Change the byte pair "facility, event" id for a short combining the
  26 informatinon.<br>
  27 (4) Statistics per time window.<br>
  28 (4) Disable plugins when threshold reached (i.e. too much process in control
  29 flow view). Draw, and, when the threshold is reached, stop drawing. The global
  30 statistics view can inhibit showing the per process stats.<br>
  31 (4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
  32 cpus > 0.<br>
  33 (4) Add event specific fields support to filter.<br>
  34 (4) Add a periodic event interval view. (useful to verify event periodicity)<br>
  35 (4) create a graphical per cpu activity view.<br>
  36 (4) Filter by target process.<br>
  37 (4) Compensate for time spent in probes in LTTV analysis.<br>
  38 (4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
  39 (5) Add Python scripting hooks.<br>
  40 (5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
  41 (5) Automatically detect traces with too much processes and disable faulty operations.<br>
  42 (5) Event sequence detector (inspired from regular expressions).<br>
  43 (7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
  44 page faults, interrupts...). This will be a generalisation of the event rate
  45 view into a view of the evolution of a user definable event field.<br>
  46 <br>
  47 * TO FIX<br>
  48 (10) Add cancel button to LTTV filter GUI window.<br>
  49 (10) Sometimes, in the control flow view, a process with 0 creation time is
  50 created in addition to the real process itself. Seems to be caused by end of
  51 process life.<br>
  52 (10) Statistics do not take in account the time spent in the mode present at
  53 the beginning of the trace. Example : real time spent in system call on behalf
  54 of process 0.<br>
  55 <br>
  56 <br>
  57 <big>LTT Next Generation Roadmap<small><br>
  58 <br>
  59 * TODO<br>
  60 (3) Find a way to make logging know when it causes a minor page fault
  61 recursively (without ignoring silently all nested events).<br>
  62 (3) Have various subbuffer sizes for high and low rate channels.<br>
  63 (3) Change the byte pair "facility, event" id for a short combining the
  64 informatinon.<br>
  65 (3) Add sysenter instrumentation on x86. Verify x86_64.<br>
  66 (3) #IBM Fix ppc64 syscall time accounting. Maybe caused by a missing syscall
  67 return instrumentation ?<br>
  68 (3) Process and kernel stack dump for x86_64, for native and compat.<br>
  69 (4) Add Xen support.<br>
  70         # <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
  71         # <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
  72 (4) efficient dynamic event filtering while recording trace.<br>
  73         % Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
  74 (4) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.<br>
  75 (4) In flight recorder mode, have the low traffic channels saved as normal
  76 tracefiles and high traffic channels being flight recorder.<br>
  77 (4) Try to use my own non LOCK prefixed version of atomic operations : we are
  78 using per-CPU variables, so it should make it possible.<br>
  79 (4) integrate NPTL instrumentation (see
  80 <A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
  81 (4) Probe calibration kernel module.<br>
  82 (5) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
  83 (5) Move to DebugFS for channel files.<br>
  84 (5) Support CPUs with scalable frequency.<br>
  85 (5) Integrate LTTng and lttd with LKCD.<br>
  86 (7) Integrate periodical dump of perfctr hardware counters.<br>
  87 (8) Integrate periodical dump of SystemTAP computed information.<br>
  88 (8) Integrate SystemTAP logging with LTTng.<br>
  89 (9) Add support for setjmp/longjmp and jump tables instrumentation to
  90 ltt-instrument-functions.<br>
  91 (9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
  92 (3) port LTTng to :<br>
  93 alpha<BR>
  94 user-mode Linux<BR>
  95 Xen<BR>
  96 # IBM<BR>
  97 S/390<BR>
  98 RTLinux<BR>
  99 % Wind River for 2.6.14<BR>
 100 <br>
 101 <br>
 102 <br>
 103 * TODO (low priority)<br>
 104 enhance RPM packages for lttng kernel<br>
 105 Integrate header generation (genevent) in kernel build system.<br>
 106 Export channels via network sockets instead of writing them to disk.<br>
 107 Export buffers with time constraint for "live" visualisation. Use
 108 ltt_force_switch periodically from a timer to insure slow channels do not
 109 interfere with viewing.<br>
 110 Have an optional round-robin mode to write information into multiple channels
 111 from the same source.<br>
 112 <br>
 113 * Need to be discussed<br>
 114 Use 2.6.14 RelayFS control files.<br>
 115 Drop ltt-module-register and ltt-module-unregister, use exported variables.<br>
 116 drop ltt_filter_control, use functions pointers instead.<br>
 117 Merge facilities headers into one big header.<br>
 118 Change the name of XML files from XML to something else.<br>
 119 Remove ltt-base.c.<br>
 120 <br>
 121 <br>
 122 * lttng patch division (0.5.10+) :<br>
 123 <br>
 124 instrumentation.diff<br>
 125 instrumentation-arm.diff<br>
 126 instrumentation-i386.diff<br>
 127 instrumentation-mips.diff<br>
 128 instrumentation-powerpc.diff<br>
 129 instrumentation-ppc.diff<br>
 130 instrumentation-s390.diff<br>
 131 instrumentation-sh.diff<br>
 132 ltt-facilities-headers.diff<br>
 133 ltt-facilities-loader.diff<br>
 134 ltt-facilities.diff<br>
 135 ltt-relayfs.diff<br>
 136 ltt-core.diff<br>
 137 ltt-build.diff<br>
 138 <br>
 139 <br>
 140 Mathieu Desnoyers<br>
 141
 142
 143 </body>
 144 </html>