Searched refs:traced (Results 1 – 25 of 30) sorted by relevance
12
| /linux-5.19.10/arch/s390/kernel/ |
| D | mcount.S | 36 stg %r14,(__SF_GPRS+8*8)(%r15) # save traced function caller
|
| /linux-5.19.10/Documentation/trace/ |
| 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 | fprobe.rst | 105 This is the ftrace address of the traced function (both entry and exit).
112 in the entry_handler. If you need traced instruction pointer, you need
154 which is traced by other ftrace users is called from the entry_handler.
|
| D | ftrace.rst | 231 to be traced. Echoing names of functions into this file
252 be traced. If a function exists in both set_ftrace_filter
253 and set_ftrace_notrace, the function will _not_ be traced.
263 traced by the function tracer as well. This option will also
274 traced by the function tracer as well. This option will also
278 file takes precedence, and the thread will not be traced.
297 be traced.
310 what functions are being traced.
330 have been converted to nops and are available to be traced.
343 If the callback registered to be traced by a function with
[all …]
|
| D | events.rst | 15 Not all tracepoints can be traced using the event tracing system;
353 but just will not be traced, unless of course it's actually enabled.
403 That is, the tracepoint will be called, but just will not be traced.
408 traced when a read system call is entered, and the :1 at the end
414 The following trigger causes kmalloc events to stop being traced
887 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/debug/tracing/trace.
|
| D | kprobetrace.rst | 239 And you can see the traced information via /sys/kernel/debug/tracing/trace.
|
| /linux-5.19.10/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-5.19.10/Documentation/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-5.19.10/Documentation/input/devices/ |
| D | appletouch.rst | 81 full tracing (each sample is being traced)::
|
| /linux-5.19.10/Documentation/core-api/ |
| D | entry.rst | 177 code to be traced, while also maintaining symmetry with irq_exit_rcu() and
227 traced.
|
| /linux-5.19.10/arch/arc/kernel/ |
| D | entry.S | 317 ; (ii) If signal is SIGTRAP/SIGSTOP, task is being traced thus
|
| /linux-5.19.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-filter.txt | 32 Filters can be attached to traced events. They can be used to filter out various
|
| /linux-5.19.10/tools/perf/Documentation/ |
| D | perf-script.txt | 462 Use with -S or --symbols to list traced records within address range.
464 For example, to list the traced records within the address range
|
| D | perf-intel-pt.txt | 752 In per-thread mode an exact list of threads is traced. There is no inheritance.
756 option, or processes selected with -p or -u) are traced. Each cpu has its own
759 In workload-only mode, the workload is traced but with per-cpu buffers.
1102 PSB+ occurs while control flow is being traced.
1621 Can be compiled and traced:
|
| D | perf-record.txt | 142 - 'filter': defines a region that will be traced.
|
| /linux-5.19.10/Documentation/virt/kvm/ |
| D | locking.rst | 68 R/X bits if for an access-traced spte, or both. This is safe because whenever
|
| /linux-5.19.10/Documentation/dev-tools/ |
| D | kmemleak.rst | 85 friends are traced and the pointers, together with additional
|
| /linux-5.19.10/Documentation/driver-api/usb/ |
| D | dwc3.rst | 667 operations, both of which can be traced. Format is::
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-kernel-slab | 489 should be traced.
|
| /linux-5.19.10/drivers/scsi/qla2xxx/ |
| D | qla_target.c | 1057 bool traced = false; in qlt_free_session_done() local
1061 if (!traced) { in qlt_free_session_done()
1065 traced = true; in qlt_free_session_done()
|
| /linux-5.19.10/kernel/trace/ |
| D | Kconfig | 590 when the likelys and unlikelys are not being traced.
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | proc.rst | 243 T is traced or stopped)
332 uninterruptible wait, Z is zombie, T is traced or stopped)
|
12