Searched refs:traced (Results 1 – 25 of 33) sorted by relevance
12
| /linux-6.12.1/Documentation/trace/ |
| 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
|
| D | fprobe.rst | 107 This is the ftrace address of the traced function (both entry and exit).
112 This is the return address that the traced function will return to,
118 in the entry_handler. If you need traced instruction pointer, you need
166 which is traced by other ftrace users is called from the entry_handler.
|
| 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
|
| D | ftrace.rst | 267 to be traced. Echoing names of functions into this file
288 be traced. If a function exists in both set_ftrace_filter
289 and set_ftrace_notrace, the function will _not_ be traced.
299 traced by the function tracer as well. This option will also
310 traced by the function tracer as well. This option will also
314 file takes precedence, and the thread will not be traced.
333 be traced.
346 what functions are being traced.
372 have been converted to nops and are available to be traced.
385 If the callback registered to be traced by a function with
[all …]
|
| 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.
|
| D | events.rst | 15 Not all tracepoints can be traced using the event tracing system;
379 but just will not be traced, unless of course it's actually enabled.
429 That is, the tracepoint will be called, but just will not be traced.
434 traced when a read system call is entered, and the :1 at the end
440 The following trigger causes kmalloc events to stop being traced
913 Finally, the event won't be actually traced until it's 'closed',
|
| D | uprobetracer.rst | 171 And you can see the traced information via /sys/kernel/tracing/trace.
|
| D | fprobetrace.rst | 213 For example, usually ``task_struct::start_time`` is not traced, but with this
|
| /linux-6.12.1/arch/s390/kernel/ |
| D | mcount.S | 47 stg %r14,(__SF_GPRS+8*8)(%r15) # save traced function caller
|
| /linux-6.12.1/Documentation/livepatch/ |
| 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
|
| D | livepatch.rst | 413 - Only functions that can be traced could be patched.
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | legacy_instructions.rst | 25 usage of emulated instruction is traced as well as rate limited
|
| D | memory-tagging-extension.rst | 209 - ``-EPERM`` - the specified process cannot be traced.
|
| /linux-6.12.1/Documentation/input/devices/ |
| D | appletouch.rst | 81 full tracing (each sample is being traced)::
|
| /linux-6.12.1/Documentation/core-api/ |
| D | entry.rst | 177 code to be traced, while also maintaining symmetry with irq_exit_rcu() and
227 traced.
|
| /linux-6.12.1/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 12 instructions that were traced for debugging or profiling purposes. You
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | perf-script.txt | 481 Use with -S or --symbols to list traced records within address range.
483 For example, to list the traced records within the address range
|
| D | perf-intel-pt.txt | 765 In per-thread mode an exact list of threads is traced. There is no inheritance.
769 option, or processes selected with -p or -u) are traced. Each cpu has its own
772 In workload-only mode, the workload is traced but with per-cpu buffers.
1137 PSB+ occurs while control flow is being traced.
1829 Can be compiled and traced:
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | workload-tracing.rst | 41 is traced. Any error paths in that system call will not be traced. If there
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kmemleak.rst | 85 friends are traced and the pointers, together with additional
|
| /linux-6.12.1/Documentation/virt/kvm/ |
| D | locking.rst | 88 R/X bits if for an access-traced spte, or both. This is safe because whenever
|
| /linux-6.12.1/mm/ |
| D | Kconfig.debug | 250 detector. The memory allocation/freeing is traced in a way
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | dwc3.rst | 667 operations, both of which can be traced. Format is::
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-kernel-slab | 489 should be traced.
|
| /linux-6.12.1/drivers/scsi/qla2xxx/ |
| D | qla_target.c | 1040 bool traced = false; in qlt_free_session_done() local
1044 if (!traced) { in qlt_free_session_done()
1048 traced = true; in qlt_free_session_done()
|
12