[ust.git] / TODO

- support multiple simultaneous traces
- fix FIXME's in the code
- add compilation tests
- test with smaller subbuffer sizes
- correctly destroy buffers at trace destroy
- add option to see subbuffer size and count
- performance testing tool (in progress by Rafik Fahem)
- profile with oprofile or similar to check for perf bottlenecks
- improve support for combined kernel/userspace tracing
- document API
- make sure the proper structures are cacheline aligned, and test performance, including multi-threaded
- fix header/lib priority problem at compilation
- port changes from recent versions of lttng kernel
- make cli interface for flight recorder
- save_registers: save them only when the marker is active (complicated because we need to know their value at the address that is put in struct marker)
- make streaming work, including periodical flush
- make a system (signal-based?) that allow the listener thread to not be started initially
- ustd should work as a pool of threads
- support more than one marker with the same channel and name on the same line?
- make a mode where the listener thread can poll buffers to check if they are ready to be collected
  This is to guarantee there will never be a system call in the tracing path. Currently there is a system
  call when the buffer is full to notify the listener it can be collected.
- In early tracing mode, the only channels that can be used reliably are "metadata" and "ust". The "usttrace" tool always uses early tracing and is hence subject to this limitation. Traces setup with the "ustctl" tool ("manual mode") are not subject to this limitation and can contain channels that have any name. Also, when loading a library with dlopen(), in order for markers in the library to generate events in the trace, these markers must be in the same channel as an event that was in the executable or its dynamically linked libraries that were loaded at start time. If using early tracing, only the "ust" channel can be used. Fix this. (RCU locking of channel structures in progress by Mathieu Desnoyers)
Commit	Line	Data
5a5151f4 PMF	1	- support multiple simultaneous traces
5a5151f4 PMF	2	- fix FIXME's in the code
27a4f279	3	- add compilation tests
5a5151f4	4	- test with smaller subbuffer sizes
f9e2cafd	5	- correctly destroy buffers at trace destroy
1808a771	6	- add option to see subbuffer size and count
3b74716b	7	- performance testing tool (in progress by Rafik Fahem)
92b339a9	8	- profile with oprofile or similar to check for perf bottlenecks
3b74716b	9	- improve support for combined kernel/userspace tracing
972af454	10	- document API
1e066c2d	11	- make sure the proper structures are cacheline aligned, and test performance, including multi-threaded
eb4870e6	12	- fix header/lib priority problem at compilation
5a5151f4	13	- port changes from recent versions of lttng kernel
eb4870e6	14	- make cli interface for flight recorder
eb4870e6	15	- save_registers: save them only when the marker is active (complicated because we need to know their value at the address that is put in struct marker)
a0c822d0	16	- make streaming work, including periodical flush
5a5151f4	17	- make a system (signal-based?) that allow the listener thread to not be started initially
17183f1c	18	- ustd should work as a pool of threads
a0c822d0	19	- support more than one marker with the same channel and name on the same line?
1808a771 PMF	20	- make a mode where the listener thread can poll buffers to check if they are ready to be collected
	21	This is to guarantee there will never be a system call in the tracing path. Currently there is a system
	22	call when the buffer is full to notify the listener it can be collected.
a0c822d0	23	- In early tracing mode, the only channels that can be used reliably are "metadata" and "ust". The "usttrace" tool always uses early tracing and is hence subject to this limitation. Traces setup with the "ustctl" tool ("manual mode") are not subject to this limitation and can contain channels that have any name. Also, when loading a library with dlopen(), in order for markers in the library to generate events in the trace, these markers must be in the same channel as an event that was in the executable or its dynamically linked libraries that were loaded at start time. If using early tracing, only the "ust" channel can be used. Fix this. (RCU locking of channel structures in progress by Mathieu Desnoyers)