| /linux-6.15/Documentation/trace/ |
| H A D | hisi-ptt.rst | 115 Link. You can choose to filter the traced headers by either Requester ID,
132 direction of inbound and traced data format of 8DW.
210 You can change the format of the traced TLP headers by specifying the
217 The traced TLP header format is different from the PCIe standard.
261 The traced TLP headers will be written to the memory allocated
280 You can decode the traced data with `perf report -D` command (currently
281 only support to dump the raw trace data). The traced data will be decoded
|
| H A D | ftrace-uses.rst | 93 This is the instruction pointer of the function that is being traced.
98 the function being traced (where the call of the function occurred).
115 called by a callback may also be traced, and call that same callback,
200 the traced function (have another function called instead of the
201 traced function), it requires setting this flag. This is what live
293 to be traced.
301 functions it finds to not be traced. This is a separate list from the
|
| H A D | fprobe.rst | 110 This is the ftrace address of the traced function (both entry and exit).
115 This is the return address that the traced function will return to,
178 which is traced by other ftrace users is called from the entry_handler.
|
| H A D | ftrace.rst | 333 be traced.
346 what functions are being traced.
422 traced.
1138 function as well as the function being traced.
1379 displayed after each function traced. The
1384 calls exceeds that, the function is not traced.
1401 when a task is traced in and out during a context
1415 interrupt will not be traced.
1424 When set, the return value of each traced function
2933 can be traced.
[all …]
|
| H A D | kprobetrace.rst | 101 Char type can be used to show the character value of traced arguments.
267 And you can see the traced information via /sys/kernel/tracing/trace.
|
| H A D | events.rst | 15 Not all tracepoints can be traced using the event tracing system;
403 but just will not be traced, unless of course it's actually enabled.
453 That is, the tracepoint will be called, but just will not be traced.
458 traced when a read system call is entered, and the :1 at the end
464 The following trigger causes kmalloc events to stop being traced
937 Finally, the event won't be actually traced until it's 'closed',
|
| H A D | uprobetracer.rst | 171 And you can see the traced information via /sys/kernel/tracing/trace.
|
| H A D | fprobetrace.rst | 213 For example, usually ``task_struct::start_time`` is not traced, but with this
|
| /linux-6.15/arch/s390/kernel/ |
| H A D | mcount.S | 47 stg %r14,(__SF_GPRS+8*8)(%r15) # save traced function caller
|
| /linux-6.15/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 203 While the traced function runs its return address on the stack points to
208 When the traced function returns to return_to_handler, there is no longer a
236 Similarly, the arm64 implementation of DYNAMIC_FTRACE_WITH_REGS patches traced
246 start of the trampoline, the address of the traced function is in X9 rather
280 this function twice, and if the function return is being traced, the unwinder
|
| H A D | livepatch.rst | 413 - Only functions that can be traced could be patched.
|
| /linux-6.15/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 25 usage of emulated instruction is traced as well as rate limited
|
| H A D | memory-tagging-extension.rst | 209 - ``-EPERM`` - the specified process cannot be traced.
|
| /linux-6.15/Documentation/input/devices/ |
| H A D | appletouch.rst | 81 full tracing (each sample is being traced)::
|
| /linux-6.15/Documentation/core-api/ |
| H A D | entry.rst | 177 code to be traced, while also maintaining symmetry with irq_exit_rcu() and
227 traced.
|
| /linux-6.15/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 12 instructions that were traced for debugging or profiling purposes. You
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 41 is traced. Any error paths in that system call will not be traced. If there
|
| /linux-6.15/tools/perf/Documentation/ |
| H A D | perf-script.txt | 490 Use with -S or --symbols to list traced records within address range.
492 For example, to list the traced records within the address range
|
| H A D | perf-intel-pt.txt | 819 In per-thread mode an exact list of threads is traced. There is no inheritance.
823 option, or processes selected with -p or -u) are traced. Each cpu has its own
826 In workload-only mode, the workload is traced but with per-cpu buffers.
1191 PSB+ occurs while control flow is being traced.
1883 Can be compiled and traced:
|
| /linux-6.15/Documentation/virt/kvm/ |
| H A D | locking.rst | 88 R/X bits if for an access-traced spte, or both. This is safe because whenever
|
| /linux-6.15/Documentation/dev-tools/ |
| H A D | kmemleak.rst | 85 friends are traced and the pointers, together with additional
|
| /linux-6.15/mm/ |
| H A D | Kconfig.debug | 251 detector. The memory allocation/freeing is traced in a way
|
| /linux-6.15/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 667 operations, both of which can be traced. Format is::
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-slab | 489 should be traced.
|
| /linux-6.15/Documentation/admin-guide/mm/damon/ |
| H A D | usage.rst | 632 Operation Scheme was about to be applied at the traced time. The first five
|