+(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
+file.<br>
+ # <A HREF="mailto:Gabriel Matni <gabrien.matni@polymtl.ca>">Gabriel
+ # Matni</A><br>
+(3) Use a per architecture enumeration for traps.<br>
+(3) Change the byte pair "facility, event" id for a short combining the
+informatinon.<br>
+(4) Statistics per time window.<br>
+(4) Add Xen per physical CPU view.<br>
+(4) Add Xen per vcpu view.<br>
+(4) Disable plugins when threshold reached (i.e. too much process in control
+flow view). Draw, and, when the threshold is reached, stop drawing. The global
+statistics view can inhibit showing the per process stats.<br>
+(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
+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) 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>
+(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
+page faults, interrupts...). This will be a generalisation of the event rate
+view into a view of the evolution of a user definable event field.<br>
+<br>
+* TO FIX<br>
+(10) Add cancel button to LTTV filter GUI window.<br>
+(10) Sometimes, in the control flow view, a process with 0 creation time is
+created in addition to the real process itself. Seems to be caused by end of
+process life.<br>
+(10) Statistics do not take in account the time spent in the mode present at
+the beginning of the trace. Example : real time spent in system call on behalf
+of process 0.<br>