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

<html>
<body>
<center><big><big>LTTV & LTTng roadmap<small><small></center>
<br>
<br>
Here are the roadmaps for the LTTV and LTTng development. I use a priority indice
for the TODO items :<br>
(1) : very high priority<br>
(10): lowest priority<br>
<br>
<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>
(2) Finish pre-computing of states to a file.<br>
(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>
(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) 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) 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>
<br>
<br>
<big>LTT Next Generation Roadmap<small><br>
<br>
* TODO<br>
(3) Add sysenter instrumentation on x86. Verify x86_64.<br>
(3) Have various subbuffer sizes for high and low rate channels.<br>
(3) Change the byte pair "facility, event" id for a short combining the
informatinon.<br>
(4) Add Xen support.<br>
	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
	# <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</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) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.<br>
(4) In flight recorder mode, have the low traffic channels saved as normal
tracefiles and high traffic channels being flight recorder.<br>
(4) Try to use my own non LOCK prefixed version of atomic operations : we are
using per-CPU variables, so it should make it possible.<br>
(4) integrate NPTL instrumentation (see
<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
(4) Probe calibration kernel module.<br>
(4) Make page faults detect nested fault without nesting 4 times in the page
fault handler.<br>
(4) #IBM Test fix for ppc64 kernel 2.6.9 missing syscall return instrumentation.<br>
(5) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
(5) Move to DebugFS for channel files.<br>
(5) Support CPUs with scalable frequency.<br>
(5) Integrate LTTng and lttd with LKCD.<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>
(9) Add support for setjmp/longjmp and jump tables instrumentation to
ltt-instrument-functions.<br>
(9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
(3) port LTTng to :<br>
alpha<BR>
user-mode Linux<BR>
Xen<BR>
# IBM<BR>
S/390<BR>
RTLinux<BR>
% Wind River for 2.6.14<BR>
<br>
<br>
<br>
* TODO (low priority)<br>
enhance RPM packages for lttng kernel<br>
Integrate header generation (genevent) in kernel build system.<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 do not
interfere with viewing.<br>
Have an optional round-robin mode to write information into multiple channels
from the same source.<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>
Change the name of XML files from XML to something else.<br>
Remove ltt-base.c.<br>
<br>
<br>
* lttng patch division (0.5.10+) :<br>
<br>
instrumentation.diff<br>
instrumentation-arm.diff<br>
instrumentation-i386.diff<br>
instrumentation-mips.diff<br>
instrumentation-powerpc.diff<br>
instrumentation-ppc.diff<br>
instrumentation-s390.diff<br>
instrumentation-sh.diff<br>
ltt-facilities-headers.diff<br>
ltt-facilities-loader.diff<br>
ltt-facilities.diff<br>
ltt-relayfs.diff<br>
ltt-core.diff<br>
ltt-build.diff<br>
<br>
<br>
Mathieu Desnoyers<br>


</body>
</html>
Commit	Line	Data
1f2c88b1	1	<html>
1f2c88b1	2	<body>
e3a30a9e	3	<center><big><big>LTTV & LTTng roadmap<small><small></center>
674fa3b3	4	<br>
674fa3b3	5	<br>
5e11a375	6	Here are the roadmaps for the LTTV and LTTng development. I use a priority indice
fc5993d2	7	for the TODO items :<br>
90d65afc	8	(1) : very high priority<br>
90d65afc	9	(10): lowest priority<br>
fc5993d2	10	<br>
fc5993d2	11	<br>
6b18b620	12	Dependencies are written between brackets [ ].<br>
59656e3f	13	The # symbol marks who is currently working on the item.<br>
e565223b	14	The % symbol marks who is interested in the realisation of the item.<br>
59656e3f	15	<br>
c8a111eb	16	<big>LTTV Roadmap<small><br>
	17	<br>
	18	* TODO<br>
9f95f0a6	19	(2) Finish pre-computing of states to a file.<br>
162990b3	20	(3) Add cluster support.<br>
162990b3	21	# <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
ef19b009	22	(3) Make LTTV aware of type formats (visual separators) defined in the XML
ef19b009	23	file.<br>
15b0e8a4	24	(3) Use a per architecture enumeration for traps.<br>
568c21ab	25	(3) Change the byte pair "facility, event" id for a short combining the
568c21ab	26	informatinon.<br>
3ccb19e4	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>
568c21ab	31	(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
568c21ab	32	cpus > 0.<br>
16fe6efa	33	(4) Add event specific fields support to filter.<br>
6ed34001	34	(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
2d569f51	35	(4) create a graphical per cpu activity view.<br>
e6284587	36	(4) Filter by target process.<br>
cdee9265	37	(4) Compensate for time spent in probes in LTTV analysis.<br>
568c21ab	38	(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
b35779fc	39	(5) Add Python scripting hooks.<br>
b0a1cd56	40	(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
caf22319	41	(5) Automatically detect traces with too much processes and disable faulty operations.<br>
b0a1cd56	42	(5) Event sequence detector (inspired from regular expressions).<br>
c5cab5d9	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>
b85b85e5	46	<br>
162990b3	47	* TO FIX<br>
b85b85e5	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>
5355b763	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>
c8a111eb	55	<br>
c8a111eb	56	<br>
c8a111eb	57	<big>LTT Next Generation Roadmap<small><br>
0c4b3d55	58	<br>
c8a111eb	59	* TODO<br>
a7bdb436	60	(3) Add sysenter instrumentation on x86. Verify x86_64.<br>
b4b2bb06	61	(3) Have various subbuffer sizes for high and low rate channels.<br>
568c21ab	62	(3) Change the byte pair "facility, event" id for a short combining the
568c21ab	63	informatinon.<br>
285468d4	64	(4) Add Xen support.<br>
51096bff	65	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
285468d4	66	# <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
59ce71d0	67	(4) efficient dynamic event filtering while recording trace.<br>
59ce71d0	68	% Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
1e5a121c	69	(4) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.<br>
cf7147c5	70	(4) In flight recorder mode, have the low traffic channels saved as normal
cf7147c5	71	tracefiles and high traffic channels being flight recorder.<br>
568c21ab	72	(4) Try to use my own non LOCK prefixed version of atomic operations : we are
568c21ab	73	using per-CPU variables, so it should make it possible.<br>
1e5a121c	74	(4) integrate NPTL instrumentation (see
1e5a121c	75	<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
cdee9265	76	(4) Probe calibration kernel module.<br>
a7bdb436	77	(4) Make page faults detect nested fault without nesting 4 times in the page
	78	fault handler.<br>
	79	(4) #IBM Test fix for ppc64 kernel 2.6.9 missing syscall return instrumentation.<br>
cdee9265	80	(5) Discuss with RelayFS upstream to integrate LTTng modifications.<br>
cdee9265	81	(5) Move to DebugFS for channel files.<br>
3f43b8fb	82	(5) Support CPUs with scalable frequency.<br>
2a341212	83	(5) Integrate LTTng and lttd with LKCD.<br>
575b7e97	84	(7) Integrate periodical dump of perfctr hardware counters.<br>
cc5ce8a0	85	(8) Integrate periodical dump of SystemTAP computed information.<br>
cc5ce8a0	86	(8) Integrate SystemTAP logging with LTTng.<br>
9fd0275c	87	(9) Add support for setjmp/longjmp and jump tables instrumentation to
451c9b19	88	ltt-instrument-functions.<br>
51096bff	89	(9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
6b18b620	90	(3) port LTTng to :<br>
e565223b	91	alpha<BR>
	92	user-mode Linux<BR>
	93	Xen<BR>
841c926b	94	# IBM<BR>
e565223b	95	S/390<BR>
d804e215	96	RTLinux<BR>
d804e215	97	% Wind River for 2.6.14<BR>
0c4b3d55	98	<br>
15e89ad6	99	<br>
b720b182	100	<br>
b720b182	101	* TODO (low priority)<br>
cbe85414	102	enhance RPM packages for lttng kernel<br>
b720b182	103	Integrate header generation (genevent) in kernel build system.<br>
63eeefc3	104	Export channels via network sockets instead of writing them to disk.<br>
63eeefc3	105	Export buffers with time constraint for "live" visualisation. Use
6b18b620	106	ltt_force_switch periodically from a timer to insure slow channels do not
63eeefc3	107	interfere with viewing.<br>
44397e24	108	Have an optional round-robin mode to write information into multiple channels
44397e24	109	from the same source.<br>
b720b182	110	<br>
15e89ad6	111	* Need to be discussed<br>
af3cfedc	112	Use 2.6.14 RelayFS control files.<br>
b720b182	113	Drop ltt-module-register and ltt-module-unregister, use exported variables.<br>
b720b182	114	drop ltt_filter_control, use functions pointers instead.<br>
b720b182	115	Merge facilities headers into one big header.<br>
	116	Change the name of XML files from XML to something else.<br>
	117	Remove ltt-base.c.<br>
	118	<br>
b720b182	119	<br>
2966f052	120	* lttng patch division (0.5.10+) :<br>
2966f052	121	<br>
451c9b19	122	instrumentation.diff<br>
	123	instrumentation-arm.diff<br>
	124	instrumentation-i386.diff<br>
	125	instrumentation-mips.diff<br>
	126	instrumentation-powerpc.diff<br>
	127	instrumentation-ppc.diff<br>
	128	instrumentation-s390.diff<br>
	129	instrumentation-sh.diff<br>
b720b182	130	ltt-facilities-headers.diff<br>
	131	ltt-facilities-loader.diff<br>
	132	ltt-facilities.diff<br>
b720b182	133	ltt-relayfs.diff<br>
b720b182	134	ltt-core.diff<br>
2966f052	135	ltt-build.diff<br>
b720b182	136	<br>
	137	<br>
	138	Mathieu Desnoyers<br>
1f2c88b1	139
	140
	141	</body>
	142	</html>