Lines Matching full:trace

16 The trace feature uses GCC's instrument-functions feature to trace all
22 which extracts useful information from it. The resulting trace output
48 Run sandbox, wait for a bit of trace information to appear, and then capture
49 a trace:
57 trace: enabled
63 =>trace stats
71 =>trace stats
79 =>trace calls 0 e00000
91 =>sb save host 0 trace 0 ${profoffset}
96 Then run proftool to convert the trace information to ftrace format.
98 $ ./sandbox/tools/proftool -m sandbox/System.map -p trace dump-ftrace >trace.txt
102 $ pytimechart trace.txt
104 Using this tool you can zoom and pan across the trace, with the function
113 		Enables the trace feature in U-Boot.
116 		Enables the trace command.
119 		Size of trace buffer to allocate for U-Boot. This buffer is
128 		Size of 'early' trace buffer. Before U-Boot has relocated
129 		it doesn't have a proper trace buffer. On many boards
130 		you can define an area of memory to use for the trace
131 		buffer until the 'real' trace buffer is available after
136 		Address of early trace buffer
148 Collecting Trace Data
151 When you run U-Boot on your board it will collect trace data up to the
152 limit of the trace buffer size you have specified. Once that is exhausted
155 Collecting trace data has an affect on execution time/performance. You
172 OS. There is useful trace data in the execution of that bootm
173 command. Therefore this implementation provides a way to collect trace
177 collects the trace data and writes it somewhere.
179 Trace data collection relies on a microsecond timer, accesed through
185 __attribute__((no_instrument_function)) so that the trace library can
192 The trace command has variable sub-commands:
207 		Dump function call trace into buffer
220 		Base address of trace output buffer
223 		Offset of first unwritten byte in trace output buffer
226 		Size of trace output buffer
228 All of these are set by the 'trace calls' command.
230 These variables keep track of the amount of data written to the trace
231 output buffer by the 'trace' command. The trace commands which write data
236 	trace funclist 10000 e00000
237 	trace calls
244 		is a useful time to write the trace data to the host for
248 Writing Out Trace Data
251 Once the trace data is in an output buffer in memory there are various ways
255 fakegocmd=trace pause; usb start; set autoload n; bootp;
256 	trace calls 10000000 1000000;
260 a trace log to address 10000000 and sends it to a host machine using
265 Converting Trace Output Data
268 The trace output data is kept in a binary format which is not documented
271 This tool must be given the U-Boot map file and the trace data received
279 		Specifiy profile/trace file
287 Viewing the Trace Data
309 3. Collect the trace information as descibed above. Use this to find where
321 Configuring Trace
327 The maximum depth reached is recorded and displayed by the 'trace stats'
335 run-time configuration options for trace.
339 - Trace filter to select which functions are recorded
341 - Better control over trace depth
342 - Compression of trace information