[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>
(1) Marker integration. Change the byte pair "facility, event" id for a short
combining the informatinon.<br>
	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><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>
	# <A HREF="mailto:Gabriel Matni <gabrien.matni@polymtl.ca>">Gabriel Matni</A><br>
(3) Use a per architecture enumeration for traps.<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>
(4) Add sort by process priority in the control flow view (must also instrument
priority information of the processes).<br>
% Airbus<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>
<br>
<br>
<big>LTT Next Generation Roadmap<small><br>
<br>
* TODO<br>
(1) efficient dynamic event filtering while recording trace.<br>
	% Google<br>
	% Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
	- Partly implemented: per marker selection through /proc interface.<br>
	- Must still implement per active trace filtering.<br>
(1) Add Xen support. (Trace buffer desallocation needs to be fixed)<br>
	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
(1) Integrate SystemTAP logging with LTTng.<br>
(4) instrument kernel bottom half irqsave, seqlocks, semaphores, mutexes, brlock.<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>
(5) Support CPUs with scalable frequency.<br>
(5) Add boot time tracing support.<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>
(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>
sparc64<BR>
# Wind River<BR>
sh4<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>
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>
e0bf2461	19	(1) Marker integration. Change the byte pair "facility, event" id for a short
	20	combining the informatinon.<br>
	21	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
162990b3	22	(3) Add cluster support.<br>
162990b3	23	# <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
ef19b009	24	(3) Make LTTV aware of type formats (visual separators) defined in the XML
ef19b009	25	file.<br>
9f8804eb	26	# <A HREF="mailto:Gabriel Matni <gabrien.matni@polymtl.ca>">Gabriel Matni</A><br>
15b0e8a4	27	(3) Use a per architecture enumeration for traps.<br>
3ccb19e4	28	(4) Statistics per time window.<br>
ea53f068	29	(4) Add Xen per physical CPU view.<br>
ea53f068	30	(4) Add Xen per vcpu view.<br>
3ccb19e4	31	(4) Disable plugins when threshold reached (i.e. too much process in control
	32	flow view). Draw, and, when the threshold is reached, stop drawing. The global
	33	statistics view can inhibit showing the per process stats.<br>
568c21ab	34	(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
568c21ab	35	cpus > 0.<br>
16fe6efa	36	(4) Add event specific fields support to filter.<br>
6ed34001	37	(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
2d569f51	38	(4) create a graphical per cpu activity view.<br>
e6284587	39	(4) Filter by target process.<br>
cdee9265	40	(4) Compensate for time spent in probes in LTTV analysis.<br>
568c21ab	41	(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
42c475ad	42	(4) Add sort by process priority in the control flow view (must also instrument
	43	priority information of the processes).<br>
	44	% Airbus<br>
b35779fc	45	(5) Add Python scripting hooks.<br>
80f91a14	46	(5) Add GUI interface to take an hybrid trace.<br>
b0a1cd56	47	(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
caf22319	48	(5) Automatically detect traces with too much processes and disable faulty operations.<br>
b0a1cd56	49	(5) Event sequence detector (inspired from regular expressions).<br>
c5cab5d9	50	(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
	51	page faults, interrupts...). This will be a generalisation of the event rate
	52	view into a view of the evolution of a user definable event field.<br>
b85b85e5	53	<br>
162990b3	54	* TO FIX<br>
b85b85e5	55	(10) Add cancel button to LTTV filter GUI window.<br>
	56	(10) Sometimes, in the control flow view, a process with 0 creation time is
	57	created in addition to the real process itself. Seems to be caused by end of
	58	process life.<br>
5355b763	59	(10) Statistics do not take in account the time spent in the mode present at
	60	the beginning of the trace. Example : real time spent in system call on behalf
	61	of process 0.<br>
c8a111eb	62	<br>
c8a111eb	63	<br>
c8a111eb	64	<big>LTT Next Generation Roadmap<small><br>
0c4b3d55	65	<br>
c8a111eb	66	* TODO<br>
9675a7c5	67	(1) efficient dynamic event filtering while recording trace.<br>
b8597f4b	68	% Google<br>
9675a7c5	69	% Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
9675a7c5	70	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
e0bf2461	71	- Partly implemented: per marker selection through /proc interface.<br>
e0bf2461	72	- Must still implement per active trace filtering.<br>
9675a7c5	73	(1) Add Xen support. (Trace buffer desallocation needs to be fixed)<br>
ea53f068	74	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
00748255	75	(1) Integrate SystemTAP logging with LTTng.<br>
e0bf2461	76	(4) instrument kernel bottom half irqsave, seqlocks, semaphores, mutexes, brlock.<br>
1e5a121c	77	(4) integrate NPTL instrumentation (see
1e5a121c	78	<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
cdee9265	79	(4) Probe calibration kernel module.<br>
a7bdb436	80	(4) Make page faults detect nested fault without nesting 4 times in the page
a7bdb436	81	fault handler.<br>
3f43b8fb	82	(5) Support CPUs with scalable frequency.<br>
dbcdc489	83	(5) Add boot time tracing support.<br>
2a341212	84	(5) Integrate LTTng and lttd with LKCD.<br>
575b7e97	85	(7) Integrate periodical dump of perfctr hardware counters.<br>
cc5ce8a0	86	(8) Integrate periodical dump of SystemTAP computed information.<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>
9675a7c5	98	sparc64<BR>
9675a7c5	99	# Wind River<BR>
db7e253c	100	sh4<br>
0c4b3d55	101	<br>
15e89ad6	102	<br>
b720b182	103	<br>
b720b182	104	* TODO (low priority)<br>
cbe85414	105	enhance RPM packages for lttng kernel<br>
b720b182	106	Integrate header generation (genevent) in kernel build system.<br>
63eeefc3	107	Export channels via network sockets instead of writing them to disk.<br>
63eeefc3	108	Export buffers with time constraint for "live" visualisation. Use
6b18b620	109	ltt_force_switch periodically from a timer to insure slow channels do not
63eeefc3	110	interfere with viewing.<br>
44397e24	111	Have an optional round-robin mode to write information into multiple channels
44397e24	112	from the same source.<br>
b720b182	113	<br>
15e89ad6	114	* Need to be discussed<br>
af3cfedc	115	Use 2.6.14 RelayFS control files.<br>
b720b182	116	Drop ltt-module-register and ltt-module-unregister, use exported variables.<br>
b720b182	117	drop ltt_filter_control, use functions pointers instead.<br>
b720b182	118	Merge facilities headers into one big header.<br>
	119	Change the name of XML files from XML to something else.<br>
	120	Remove ltt-base.c.<br>
	121	<br>
b720b182	122	Mathieu Desnoyers<br>
1f2c88b1	123
	124
	125	</body>
	126	</html>