Searched full:trace (Results 1 – 25 of 136) sorted by relevance
123456
| /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 | 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).
272 effect) trace output. Only filters that reference just the common
320 Will only trace events for the current task.
[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 | ftrace.rst | 113 This sets or displays whether writing to the trace
128 trace:
130 This file holds the output of the trace in a human
141 The output is the same as the "trace" file but this
144 retrieved. Unlike the "trace" file, this file is a
149 "trace" file is static, and if the tracer is not
163 trace option (also in trace_options). Options may also be set
171 The maximum time is saved in this file. The max trace will also be
172 stored, and displayed by "trace". A new max trace will only be
181 Some latency tracers will record a trace whenever the
[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 | boottime-trace.rst | 12 Boot-time tracing allows users to trace boot-time process including
15 and trace instances.
37 Output trace-event data on printk buffer too.
40 Dump ftrace on Oops. If MODE = 1 or omitted, dump trace buffer
79 Set CPUMASK as trace cpu-mask.
127 end of core_initcall. This means you can trace the events from postcore_initcall.
129 after that (arch_initcall or subsys_initcall). Thus, you can trace those with
131 If you want to trace events before core_initcall, you can use the options
185 With the trigger action and kprobes, you can trace function-graph while
186 a function is called. For example, this will trace all function calls in
|
| /Documentation/trace/coresight/ |
| D | coresight-etm4x-reference.rst | 23 :Trace Registers: {CONFIGR + others}
25 Bit select trace features. See ‘mode’ section below. Bits
26 in this will cause equivalent programming of trace config and
32 bitfield up to 32 bits setting trace features.
40 :Trace Registers: All
42 Reset all programming to trace nothing / no logic programmed.
50 :Trace Registers: PRGCTLR, All hardware regs.
53 and enables trace.
55 - = 0 : disable trace hardware.
63 :Trace Registers: None.
[all …]
|
| D | coresight-trbe.rst | 4 Trace Buffer Extension (TRBE).
13 Trace Buffer Extension (TRBE) is a percpu hardware which captures in system
15 gets plugged in as a coresight sink device because the corresponding trace
|
| 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 …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | ete.yaml | 8 title: ARM Embedded Trace Extensions
15 Arm Embedded Trace Extension(ETE) is a per CPU trace component that
18 The trace generated by the ETE could be stored via legacy CoreSight
20 Arm Trace Buffer Extension (TRBE)). Since the ETE can be connected to
30 - const: arm,embedded-trace-extension
39 Output connections from the ETE to legacy CoreSight trace bus.
43 description: Output connection from the ETE to legacy CoreSight Trace bus.
57 compatible = "arm,embedded-trace-extension";
63 compatible = "arm,embedded-trace-extension";
|
| D | trbe.yaml | 8 title: ARM Trace Buffer Extensions
14 Arm Trace Buffer Extension (TRBE) is a per CPU component
15 for storing trace generated on the CPU to memory. It is
25 - const: arm,trace-buffer-extension
46 compatible = "arm,trace-buffer-extension";
|
| 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), with memory mapped access.
[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/powerpc/ |
| D | imc.rst | 92 IMC Trace-mode
95 POWER9 supports two modes for IMC which are the Accumulation mode and Trace
98 Trace mode, the 64 bit trace SCOM value is initialized with the event
99 information. The CPMCxSEL and CPMC_LOAD in the trace SCOM, specifies the event
105 whether hardware is configured for accumulation or trace mode.
115 | | 1: Trace Mode |
152 *Currently the event monitored for trace-mode is fixed as cycle.*
154 Trace IMC example usage
163 To record an application/process with trace-imc event:
173 Benefits of using IMC trace-mode
[all …]
|
| /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
16 Description: (RW) Disables write access to the Trace RAM by stopping the
19 into the Trace RAM following the trigger event is equal to the
26 Description: (Read) Defines the depth, in words, of the trace RAM in powers of
41 that is used to read entries from the Trace RAM over the APB
51 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-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: (Read) Provides the number of counters accessible on a trace unit,
164 trace unit, as specified by bit 25:24 of register ETMCCR.
170 Description: (Write) 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-etm4x | 5 Description: (RW) Enable/disable tracing on this specific trace entiry.
83 Description: (Write) 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.
421 Description: (Read) Print the content of the trace configuration register
428 Description: (Read) Print the content of the trace ID register (0x040).
[all …]
|
| /Documentation/admin-guide/media/ |
| 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/ethernet/mellanox/ |
| D | mlx5.rst | 281 mlx5 driver provides internal trace points for tracking and debugging using
282 kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst).
288 - mlx5e_configure_flower: trace flower filter actions and cookies offloaded to mlx5::
291 $ cat /sys/kernel/debug/tracing/trace
295 - mlx5e_delete_flower: trace flower filter actions and cookies deleted from mlx5::
298 $ cat /sys/kernel/debug/tracing/trace
302 - mlx5e_stats_flower: trace flower stats request::
305 $ cat /sys/kernel/debug/tracing/trace
309 - mlx5e_tc_update_neigh_used_value: trace tunnel rule neigh update value offloaded to mlx5::
312 $ 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
|
123456