[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) Add support for "stop" button in event list. (disabling event request
scheduler)<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>
(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 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>
(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) Event filter : event.time does not work.<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>
(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) integrate NPTL instrumentation (see
<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<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>
x86_64<BR>
#Autodesk <A HREF="mailto:Francois L'Archeveque <fla@discreet.com>">Francois
L'Archeveque</A> for 2.6.9 RedHat Enterprise (patch available in contrib, still
has to be ported to 2.6.14, thanks!)<BR>
# Wind River for 2.6.14<BR>
PPC<BR>
PPC64<BR>
# Wind River for 2.6.14<BR>
alpha<BR>
user-mode Linux<BR>
Xen<BR>
# IBM<BR>
MIPS<BR>
MIPS64<BR>
% Wind River for 2.6.14<BR>
# Tim Bird <A HREF="mailto:tim.bird@as.sony.com">Tim Bird</A><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>
Find a different way to printk from instrumentation : forbidden from schedule
and wakeup (causes a deadlock). -> Modify printk so it uses LTTng tracer!<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) Add support for "stop" button in event list. (disabling event request
	20	scheduler)<br>
	21	(2) Finish pre-computing of states to a file.<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>
15b0e8a4	26	(3) Use a per architecture enumeration for traps.<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>
16fe6efa	31	(4) Add event specific fields support to filter.<br>
6ed34001	32	(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
2d569f51	33	(4) create a graphical per cpu activity view.<br>
b35779fc	34	(5) Add Python scripting hooks.<br>
b0a1cd56	35	(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
caf22319	36	(5) Automatically detect traces with too much processes and disable faulty operations.<br>
b0a1cd56	37	(5) Event sequence detector (inspired from regular expressions).<br>
c5cab5d9	38	(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
	39	page faults, interrupts...). This will be a generalisation of the event rate
	40	view into a view of the evolution of a user definable event field.<br>
b85b85e5	41	<br>
162990b3	42	* TO FIX<br>
b85b85e5	43	(10) Event filter : event.time does not work.<br>
	44	(10) Add cancel button to LTTV filter GUI window.<br>
	45	(10) Sometimes, in the control flow view, a process with 0 creation time is
	46	created in addition to the real process itself. Seems to be caused by end of
	47	process life.<br>
5355b763	48	(10) Statistics do not take in account the time spent in the mode present at
	49	the beginning of the trace. Example : real time spent in system call on behalf
	50	of process 0.<br>
c8a111eb	51	<br>
c8a111eb	52	<br>
c8a111eb	53	<big>LTT Next Generation Roadmap<small><br>
0c4b3d55	54	<br>
c8a111eb	55	* TODO<br>
285468d4	56	(4) Add Xen support.<br>
51096bff	57	# <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>">Mathieu Desnoyers</A><br>
285468d4	58	# <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
59ce71d0	59	(4) efficient dynamic event filtering while recording trace.<br>
59ce71d0	60	% Sensis Corp. <A HREF="mailto:Bish, Tim <Tim.Bish@Sensis.com>">Tim Bish</A><br>
1e5a121c	61	(4) instrument kernel bottom half irqsave, spinlocks, rwlocks, seqlocks, semaphores, mutexes, brlock.<br>
	62	(4) integrate NPTL instrumentation (see
	63	<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
3f43b8fb	64	(5) Support CPUs with scalable frequency.<br>
2a341212	65	(5) Integrate LTTng and lttd with LKCD.<br>
575b7e97	66	(7) Integrate periodical dump of perfctr hardware counters.<br>
cc5ce8a0	67	(8) Integrate periodical dump of SystemTAP computed information.<br>
cc5ce8a0	68	(8) Integrate SystemTAP logging with LTTng.<br>
9fd0275c	69	(9) Add support for setjmp/longjmp and jump tables instrumentation to
451c9b19	70	ltt-instrument-functions.<br>
51096bff	71	(9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
6b18b620	72	(3) port LTTng to :<br>
e565223b	73	x86_64<BR>
e4d84ff4	74	#Autodesk <A HREF="mailto:Francois L'Archeveque <fla@discreet.com>">Francois
63eeefc3	75	L'Archeveque</A> for 2.6.9 RedHat Enterprise (patch available in contrib, still
63eeefc3	76	has to be ported to 2.6.14, thanks!)<BR>
162990b3	77	# Wind River for 2.6.14<BR>
e565223b	78	PPC<BR>
e565223b	79	PPC64<BR>
162990b3	80	# Wind River for 2.6.14<BR>
e565223b	81	alpha<BR>
	82	user-mode Linux<BR>
	83	Xen<BR>
841c926b	84	# IBM<BR>
e565223b	85	MIPS<BR>
e565223b	86	MIPS64<BR>
162990b3	87	% Wind River for 2.6.14<BR>
162990b3	88	# Tim Bird <A HREF="mailto:tim.bird@as.sony.com">Tim Bird</A><br>
e565223b	89	S/390<BR>
d804e215	90	RTLinux<BR>
d804e215	91	% Wind River for 2.6.14<BR>
0c4b3d55	92	<br>
15e89ad6	93	<br>
b720b182	94	<br>
b720b182	95	* TODO (low priority)<br>
cbe85414	96	enhance RPM packages for lttng kernel<br>
b720b182	97	Integrate header generation (genevent) in kernel build system.<br>
baffa645	98	Find a different way to printk from instrumentation : forbidden from schedule
63eeefc3	99	and wakeup (causes a deadlock). -> Modify printk so it uses LTTng tracer!<br>
	100	Export channels via network sockets instead of writing them to disk.<br>
	101	Export buffers with time constraint for "live" visualisation. Use
6b18b620	102	ltt_force_switch periodically from a timer to insure slow channels do not
63eeefc3	103	interfere with viewing.<br>
44397e24	104	Have an optional round-robin mode to write information into multiple channels
44397e24	105	from the same source.<br>
b720b182	106	<br>
15e89ad6	107	* Need to be discussed<br>
af3cfedc	108	Use 2.6.14 RelayFS control files.<br>
b720b182	109	Drop ltt-module-register and ltt-module-unregister, use exported variables.<br>
b720b182	110	drop ltt_filter_control, use functions pointers instead.<br>
b720b182	111	Merge facilities headers into one big header.<br>
	112	Change the name of XML files from XML to something else.<br>
	113	Remove ltt-base.c.<br>
	114	<br>
b720b182	115	<br>
2966f052	116	* lttng patch division (0.5.10+) :<br>
2966f052	117	<br>
451c9b19	118	instrumentation.diff<br>
	119	instrumentation-arm.diff<br>
	120	instrumentation-i386.diff<br>
	121	instrumentation-mips.diff<br>
	122	instrumentation-powerpc.diff<br>
	123	instrumentation-ppc.diff<br>
	124	instrumentation-s390.diff<br>
	125	instrumentation-sh.diff<br>
b720b182	126	ltt-facilities-headers.diff<br>
	127	ltt-facilities-loader.diff<br>
	128	ltt-facilities.diff<br>
b720b182	129	ltt-relayfs.diff<br>
b720b182	130	ltt-core.diff<br>
2966f052	131	ltt-build.diff<br>
b720b182	132	<br>
	133	<br>
	134	Mathieu Desnoyers<br>
1f2c88b1	135
	136
	137	</body>
	138	</html>