| 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 | (3) Make LTTV aware of type formats defined in the XML file.<br> |
| 20 | (3) Use a per architecture enumeration for traps.<br> |
| 21 | (3) Integrate Kernel State Dump information.<br> |
| 22 | (4) create a event rate graphical view : Will be useful in conjunction with the |
| 23 | filter.<br> |
| 24 | # <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br> |
| 25 | (4) Add event specific fields support to filter.<br> |
| 26 | (4) create a graphical per cpu activity view.<br> |
| 27 | (5) Add Python scripting hooks.<br> |
| 28 | (5) Flight recorder : start lttd automatically upon GUI trace control stop.<br> |
| 29 | (5) Automatically detect traces with too much processes and disable faulty operations.<br> |
| 30 | (5) Event sequence detector (inspired from regular expressions).<br> |
| 31 | (7) create an analysis of function time (like a precise gprof).<br> |
| 32 | -> with gcc -f inline-functions<br> |
| 33 | (7) Create a hardware counter viewer (low cost rate counters : L1 cache miss, page faults, interrupts...).<br> |
| 34 | (10) Add cancel button to LTTV filter GUI window. |
| 35 | <br> |
| 36 | <br> |
| 37 | <big>LTT Next Generation Roadmap<small><br> |
| 38 | <br> |
| 39 | * TODO<br> |
| 40 | (2) add efficient and secure user space tracing. (1 month)<br> |
| 41 | # <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br> |
| 42 | (3) integrate LTTng State Dump : missing irq and process state.<br> |
| 43 | # <A HREF="mailto:Jean-Hugues Deschenes <jean-hugues.deschenes@polymtl.ca>">Jean-Hugues Deschenes</A><br> |
| 44 | (4) efficient dynamic event filtering while recording trace.<br> |
| 45 | % Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br> |
| 46 | (4) Create the heartbeat timer LTTng module. Make sure that heartbeat events |
| 47 | never hit the facility channel. Use the complete 64 bits TSC for the facility |
| 48 | channel in every case. That's because this channel must never be overwritten |
| 49 | even in "flight recorder" mode.<br> |
| 50 | (5) Support CPUs with scalable frequency.<br> |
| 51 | (5) Integrate LTTng and lttd with LKCD.<br> |
| 52 | (6) Add Xen support.<br> |
| 53 | (7) add gcc -finstrument-functions instrumentation<br> |
| 54 | (7) Integrate periodical dump of perfctr hardware counters.<br> |
| 55 | (8) Integrate periodical dump of SystemTAP computed information.<br> |
| 56 | (8) Integrate SystemTAP logging with LTTng.<br> |
| 57 | (3) port LTTng to :<br> |
| 58 | x86_64<BR> |
| 59 | #Autodesk <A HREF="mailto:Francois L'Archeveque <fla@discreet.com>">Francois |
| 60 | L'Archeveque</A> for 2.6.9 RedHat Enterprise (patch available in contrib, still |
| 61 | has to be ported to 2.6.14, thanks!)<BR> |
| 62 | %Wind River for 2.6.14<BR> |
| 63 | PPC<BR> |
| 64 | PPC64<BR> |
| 65 | %Wind River for 2.6.14<BR> |
| 66 | alpha<BR> |
| 67 | user-mode Linux<BR> |
| 68 | Xen<BR> |
| 69 | MIPS<BR> |
| 70 | MIPS64<BR> |
| 71 | %Wind River for 2.6.14<BR> |
| 72 | ARM<BR> |
| 73 | # <A HREF="mailto:Richard Purdie <rpurdie@openedhand.com>">Richard Purdie</A><br> |
| 74 | # <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br> |
| 75 | S/390<BR> |
| 76 | <br> |
| 77 | <br> |
| 78 | <br> |
| 79 | * TODO (low priority)<br> |
| 80 | enhance RPM packages for lttng kernel<br> |
| 81 | Integrate header generation (genevent) in kernel build system.<br> |
| 82 | Multithreaded lttd.<br> |
| 83 | Find a different way to printk from instrumentation : forbidden from schedule |
| 84 | and wakeup (causes a deadlock). -> Modify printk so it uses LTTng tracer!<br> |
| 85 | Export channels via network sockets instead of writing them to disk.<br> |
| 86 | Export buffers with time constraint for "live" visualisation. Use |
| 87 | ltt_force_switch periodically from a timer to insure slow channels do not |
| 88 | interfere with viewing.<br> |
| 89 | <br> |
| 90 | * Need to be discussed<br> |
| 91 | Use 2.6.14 RelayFS control files.<br> |
| 92 | Drop ltt-module-register and ltt-module-unregister, use exported variables.<br> |
| 93 | drop ltt_filter_control, use functions pointers instead.<br> |
| 94 | Merge facilities headers into one big header.<br> |
| 95 | Change the name of XML files from XML to something else.<br> |
| 96 | Remove ltt-base.c.<br> |
| 97 | <br> |
| 98 | <br> |
| 99 | * lttng patch division (0.5.10+) :<br> |
| 100 | <br> |
| 101 | instrumentation.diff |
| 102 | instrumentation-arm.diff |
| 103 | instrumentation-i386.diff |
| 104 | instrumentation-mips.diff |
| 105 | instrumentation-powerpc.diff |
| 106 | instrumentation-ppc.diff |
| 107 | instrumentation-s390.diff |
| 108 | instrumentation-sh.diff |
| 109 | ltt-facilities-headers.diff<br> |
| 110 | ltt-facilities-loader.diff<br> |
| 111 | ltt-facilities.diff<br> |
| 112 | ltt-relayfs.diff<br> |
| 113 | ltt-core.diff<br> |
| 114 | ltt-build.diff<br> |
| 115 | <br> |
| 116 | <br> |
| 117 | Mathieu Desnoyers<br> |
| 118 | |
| 119 | |
| 120 | </body> |
| 121 | </html> |