[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>
(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) 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) Integrate SystemTAP logging with LTTng.<br>
(2) Post LTTng 0.6.x to LKML.<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) 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) CPU Hotplug support.<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) Rethink facility logging code (genevent output). Maybe unneeded because of
markers/probes mechanism.<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>
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>
162990b3	19	(3) Add cluster support.<br>
162990b3	20	# <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
ef19b009	21	(3) Make LTTV aware of type formats (visual separators) defined in the XML
ef19b009	22	file.<br>
15b0e8a4	23	(3) Use a per architecture enumeration for traps.<br>
568c21ab	24	(3) Change the byte pair "facility, event" id for a short combining the
568c21ab	25	informatinon.<br>
3ccb19e4	26	(4) Statistics per time window.<br>
	27	(4) Disable plugins when threshold reached (i.e. too much process in control
	28	flow view). Draw, and, when the threshold is reached, stop drawing. The global
	29	statistics view can inhibit showing the per process stats.<br>
568c21ab	30	(4) Add a visual artifact : PID 0 could be named swapper instead of UNNAMED for
568c21ab	31	cpus > 0.<br>
16fe6efa	32	(4) Add event specific fields support to filter.<br>
6ed34001	33	(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
2d569f51	34	(4) create a graphical per cpu activity view.<br>
e6284587	35	(4) Filter by target process.<br>
cdee9265	36	(4) Compensate for time spent in probes in LTTV analysis.<br>
568c21ab	37	(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
b35779fc	38	(5) Add Python scripting hooks.<br>
80f91a14	39	(5) Add GUI interface to take an hybrid trace.<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>
00748255	60	(1) Integrate SystemTAP logging with LTTng.<br>
abae8bb0	61	(2) Post LTTng 0.6.x to LKML.<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>
	70	(4) integrate NPTL instrumentation (see
	71	<A HREF="http://nptltracetool.sourceforge.net/">PTT</A>).<br>
cdee9265	72	(4) Probe calibration kernel module.<br>
a7bdb436	73	(4) Make page faults detect nested fault without nesting 4 times in the page
a7bdb436	74	fault handler.<br>
7c5922fc	75	(5) CPU Hotplug support.<br>
3f43b8fb	76	(5) Support CPUs with scalable frequency.<br>
dbcdc489	77	(5) Add boot time tracing support.<br>
2a341212	78	(5) Integrate LTTng and lttd with LKCD.<br>
575b7e97	79	(7) Integrate periodical dump of perfctr hardware counters.<br>
cc5ce8a0	80	(8) Integrate periodical dump of SystemTAP computed information.<br>
abae8bb0	81	(9) Rethink facility logging code (genevent output). Maybe unneeded because of
abae8bb0	82	markers/probes mechanism.<br>
9fd0275c	83	(9) Add support for setjmp/longjmp and jump tables instrumentation to
451c9b19	84	ltt-instrument-functions.<br>
51096bff	85	(9) Make ltt-usertrace-fast support internal heartbeat timer.<br>
6b18b620	86	(3) port LTTng to :<br>
e565223b	87	alpha<BR>
	88	user-mode Linux<BR>
	89	Xen<BR>
841c926b	90	# IBM<BR>
e565223b	91	S/390<BR>
d804e215	92	RTLinux<BR>
d804e215	93	% Wind River for 2.6.14<BR>
0c4b3d55	94	<br>
15e89ad6	95	<br>
b720b182	96	<br>
b720b182	97	* TODO (low priority)<br>
cbe85414	98	enhance RPM packages for lttng kernel<br>
b720b182	99	Integrate header generation (genevent) in kernel build system.<br>
63eeefc3	100	Export channels via network sockets instead of writing them to disk.<br>
63eeefc3	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	Mathieu Desnoyers<br>
1f2c88b1	116
	117
	118	</body>
	119	</html>