update roadmap

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

diff --git a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
index af79261a1a82185e8eaed1ca6f931973e8a37c24..dc444ee66c9ae08124731bc187f8f07d21daf9a3 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-roadmap.html
@@ -19,16 +19,15 @@ The % symbol marks who is interested in the realisation of the item.<br>
 (3) Make LTTV aware of type formats (visual separators) defined in the XML
 file.<br>
 (3) Use a per architecture enumeration for traps.<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>
 (4) Add event specific fields support to filter.<br>
 (4) create a graphical per cpu activity view.<br>
 (5) Add Python scripting hooks.<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...).<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>
 (10) Add cancel button to LTTV filter GUI window.
 <br>
 <br>