Searched full:trace (Results 1 – 25 of 121) sorted by relevance
12345
| /Documentation/trace/ |
| D | intel_th.rst | 4 Intel(R) Trace Hub (TH)
10 Intel(R) Trace Hub (TH) is a set of hardware blocks that produce,
11 switch and output trace data from multiple hardware and software
12 sources over several types of trace output ports encoded in System
13 Trace Protocol (MIPI STPv2) and is intended to perform full system
14 debugging. For more information on the hardware, see Intel(R) Trace
17 It consists of trace sources, trace destinations (outputs) and a
18 switch (Global Trace Hub, GTH). These devices are placed on a bus of
23 - Software Trace Hub (STH), trace source, which is a System Trace
25 - Memory Storage Unit (MSU), trace output, which allows storing
[all …]
|
| D | stm.rst | 4 System Trace Module
7 System Trace Module (STM) is a device described in MIPI STP specs as
8 STP trace stream generator. STP (System Trace Protocol) is a trace
9 protocol multiplexing data from multiple trace sources, each one of
12 hardware trace sources, others are available to software. Software
13 trace sources are usually free to pick for themselves any
16 On the receiving end of this STP stream (the decoder side), trace
18 order for the decoder to be able to make sense of the trace that
19 involves multiple trace sources, it needs to be able to map those
20 master/channel pairs to the trace sources that it understands.
[all …]
|
| D | events-msr.rst | 2 MSR Trace Events
9 Available trace points:
13 Trace MSR reads:
22 Trace MSR writes:
31 Trace RDPMC in kernel:
35 The trace data can be post processed with the postprocess/decode_msr.py script::
37 cat /sys/kernel/debug/tracing/trace | decode_msr.py /usr/src/linux/include/asm/msr-index.h
|
| D | ftrace.rst | 109 This sets or displays whether writing to the trace
124 trace:
126 This file holds the output of the trace in a human
133 The output is the same as the "trace" file but this
136 retrieved. Unlike the "trace" file, this file is a
141 "trace" file is static, and if the tracer is not
144 "trace" file, opening this file for reading will not
157 trace option (also in trace_options). Options may also be set
165 The maximum time is saved in this file. The max trace will also be
166 stored, and displayed by "trace". A new max trace will only be
[all …]
|
| D | function-graph-fold.vim | 3 " To use, :source this file while viewing a function_graph trace, or use vim's
4 " -S option to load from the command-line together with a trace. You can then
12 " single-CPU trace (e.g. trace-cmd report --cpu 1).
|
| D | events.rst | 11 Tracepoints (see Documentation/trace/tracepoints.rst) can be used
105 Each trace event has a 'format' file associated with it that contains
107 be used to parse the binary trace stream, and is also the place to
123 where offset is the offset of the field in the trace record and size
156 Trace events can be filtered in the kernel by associating boolean
158 the trace buffer, its fields are checked against the filter expression
160 'match' the filter will appear in the trace output, and an event whose
181 'format' files for trace events (see section 4).
253 effect) trace output. Only filters that reference just the common
301 Will only trace events for the current task.
[all …]
|
| D | mmiotrace.rst | 55 Check that the driver you are about to trace is not loaded.
61 Start storing the trace::
67 Load the driver you want to trace and use it. Mmiotrace will only catch MMIO
70 During tracing you can place comments (markers) into the trace by
72 This makes it easier to see which part of the (huge) trace corresponds to
92 events were lost, the trace is incomplete. You should enlarge the buffers and
105 If you are doing a trace for a driver project, e.g. Nouveau, you should also
112 and then send the .tar.gz file. The trace compresses considerably. Replace
123 an event that is recorded into the trace log. Note that ISA range mappings
133 read or written. These are stored to the trace log.
[all …]
|
| D | coresight.rst | 60 ****************** AMBA Advanced Trace Bus (ATB) ******************
76 &&&&&&&&& IIIIIII ETM = Embedded Trace Macrocell
77 ; PTM = Program Trace Macrocell
79 * ETB = Embedded Trace Buffer
80 To trace port TPIU= Trace Port Interface Unit
84 all trace data are carried out-of-band on the ATB bus. The CTM provides
100 Program Trace Macrocell
102 Embedded Trace Macrocell
104 System trace Macrocell
106 Embedded Trace Buffer
[all …]
|
| D | events-power.rst | 2 Subsystem Trace Points: power
16 Cf. include/trace/events/power.h for the events definitions.
21 1.1 Trace API
44 The event which has 'state=4294967295' in the trace is very important to the user
|
| D | events-nmi.rst | 2 NMI Trace Events
23 you some problems and you only want to trace that handler
|
| D | ftrace-uses.rst | 16 beginning of functions in order to record and trace the flow of the kernel.
145 must never trace any function that are called by the callback
174 Filtering which functions to trace
202 See Filter Commands in :file:`Documentation/trace/ftrace.rst`.
204 To just trace the schedule function:
214 To remove all the filtered functions and trace all functions:
221 Sometimes more than one function has the same name. To trace just a specific
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight.txt | 5 SoCs tracing needs. These trace components can generally be classified as
6 sinks, links and sources. Trace data produced by one or more sources flows
16 - Embedded Trace Buffer (version 1.0):
19 - Trace Port Interface Unit:
22 - Trace Memory Controller, used for Embedded Trace Buffer(ETB),
23 Embedded Trace FIFO(ETF) and Embedded Trace Router(ETR)
28 - Trace Programmable Funnel:
33 - Embedded Trace Macrocell (version 3.x) and
34 Program Flow Trace Macrocell:
37 - Embedded Trace Macrocell (version 4.x):
[all …]
|
| /Documentation/core-api/ |
| D | tracepoint.rst | 31 ``Documentation/trace/*`` directory.
36 .. kernel-doc:: include/trace/events/irq.h
42 .. kernel-doc:: include/trace/events/signal.h
48 .. kernel-doc:: include/trace/events/block.h
54 .. kernel-doc:: include/trace/events/workqueue.h
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-stm | 5 Description: (RW) Enable/disable tracing on this specific trace macrocell.
6 Enabling the trace macrocell implies it has been configured
52 Description: (RW) Holds the trace ID that will appear in the trace stream
53 coming from this trace entity.
|
| D | sysfs-bus-coresight-devices-etb10 | 5 Description: (RW) Add/remove a sink from a trace path. There can be multiple
13 Description: (RW) Disables write access to the Trace RAM by stopping the
16 into the Trace RAM following the trigger event is equal to the
23 Description: (R) Defines the depth, in words, of the trace RAM in powers of
38 that is used to read entries from the Trace RAM over the APB
48 the CoreSight bus into the Trace RAM. The value is read directly
|
| D | ppc-memtrace | 6 hardware trace macro to use. CONFIG_PPC64_HARDWARE_TRACING
41 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/trace
45 Description: This is where the hardware trace macro will output the trace
|
| D | sysfs-bus-coresight-devices-etm4x | 5 Description: (RW) Enable/disable tracing on this specific trace entiry.
83 Description: (W) Cancels all configuration on a trace unit and set it back
98 Description: (RW) Controls which PE to trace.
116 Description: (RW) Controls the insertion of global timestamps in the trace
123 Description: (RW) Controls how often trace synchronization requests occur.
142 Description: (RW) Controls instruction trace filtering.
169 Description: (RW) Controls what type of comparison the trace unit performs.
244 Description: (RW) Controls the selection of the resources in the trace unit.
366 Description: (R) Print the content of the trace configuration register
373 Description: (R) Print the content of the trace ID register (0x040).
[all …]
|
| D | sysfs-bus-intel_th-devices-pti | 12 Description: (RW) 0: PTI trace clock acts as a strobe which only toggles
13 when there is trace data to send. 1: PTI trace clock is a
|
| D | sysfs-bus-coresight-devices-etm3x | 5 Description: (RW) Enable/disable tracing on this specific trace entiry.
24 for example the access type, the kind of instruction to trace,
26 the access type register may vary on the version of the trace
119 Description: (RW) Defines which event triggers a trace.
141 various aspect of the trace entity such as time stamping,
150 on a trace unit, as specified by bit 3:0 of register ETMCCR.
156 Description: (R) Provides the number of counters accessible on a trace unit,
164 trace unit, as specified by bit 25:24 of register ETMCCR.
170 Description: (W) Cancels all configuration on a trace unit and set it back
225 Description: (RW) Holds the trace synchronization frequency value - must be
[all …]
|
| D | sysfs-bus-coresight-devices-tmc | 5 Description: (RW) Disables write access to the Trace RAM by stopping the
29 that is used to read entries from the Trace RAM over the APB
39 the CoreSight bus into the Trace RAM. The value is read directly
91 Description: (RW) Size of the trace buffer for TMC-ETR when used in SYSFS
|
| /Documentation/media/v4l-drivers/ |
| D | philips.rst | 191 trace
193 'trace' of some of the calls the module makes; it logs all items in your
196 The trace variable is a bitmask; each bit represents a certain feature.
197 If you want to trace something, look up the bit value(s) in the table
198 below, add the values together and supply that to the trace variable.
209 4 0x4 Trace open() and close() calls Off
223 For example, to trace the open() & read() functions, sum 8 + 4 = 12,
224 so you would supply trace=12 during insmod or modprobe. If
225 you want to turn the initialization and probing tracing off, set trace=0.
226 The default value for trace is 35 (0x23).
[all …]
|
| /Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 260 mlx5 driver provides internal trace points for tracking and debugging using
261 kernel tracepoints interfaces (refer to Documentation/trace/ftrase.rst).
267 - mlx5e_configure_flower: trace flower filter actions and cookies offloaded to mlx5::
270 $ cat /sys/kernel/debug/tracing/trace
274 - mlx5e_delete_flower: trace flower filter actions and cookies deleted from mlx5::
277 $ cat /sys/kernel/debug/tracing/trace
281 - mlx5e_stats_flower: trace flower stats request::
284 $ cat /sys/kernel/debug/tracing/trace
288 - mlx5e_tc_update_neigh_used_value: trace tunnel rule neigh update value offloaded to mlx5::
291 $ cat /sys/kernel/debug/tracing/trace
[all …]
|
| /Documentation/power/ |
| D | s2ram.rst | 49 which means that the last trace event was just before trying to resume
52 fix it, disable it, or trace into its resume function.
82 using this trace option.
85 quickly after the resume failure. The trace option does not use the seconds
|
| /Documentation/devicetree/bindings/clock/ |
| D | armada3700-periph-clock.txt | 20 5 setm_tmx Serial Embedded Trace Module
28 13 trace Trace
|
| /Documentation/trace/postprocess/ |
| D | decode_msr.py | 2 # add symbolic names to read_msr / write_msr in trace
3 # decode_msr msr-index.h < trace
|
12345