Searched refs:traced (Results 1 – 22 of 22) sorted by relevance
| /linux/arch/s390/kernel/ |
| H A D | mcount.S | 47 stg %r14,(__SF_GPRS+8*8)(%r15) # save traced function caller
|
| /linux/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/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/Documentation/input/devices/ |
| H A D | appletouch.rst | 81 full tracing (each sample is being traced)::
|
| /linux/Documentation/trace/ |
| 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 | 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/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 12 instructions that were traced for debugging or profiling purposes. You
|
| /linux/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
|
| H A D | kernel-parameters.txt | 1802 [FTRACE] Limit the functions traced by the function 1815 [FTRACE] Limit the top level callers functions traced
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-script.txt | 492 Use with -S or --symbols to list traced records within address range. 494 For example, to list the traced records within the address range
|
| H A D | perf-record.txt | 135 - 'filter': defines a region that will be traced.
|
| /linux/Documentation/virt/kvm/ |
| H A D | locking.rst | 90 R/X bits if for an access-traced spte, or both. This is safe because whenever
|
| /linux/mm/ |
| H A D | Kconfig.debug | 251 detector. The memory allocation/freeing is traced in a way
|
| /linux/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 667 operations, both of which can be traced. Format is::
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-slab | 490 should be traced.
|
| /linux/kernel/trace/ |
| H A D | Kconfig | 356 Enable this to allow some of the tracing infrastructure to be traced 715 when the likelys and unlikelys are not being traced.
|
| /linux/drivers/scsi/qla2xxx/ |
| H A D | qla_target.c | 1033 bool traced = false; in qlt_free_session_done() local 1037 if (!traced) { in qlt_free_session_done() 1041 traced = true; in qlt_free_session_done()
|
| /linux/arch/m68k/ifpsp060/src/ |
| H A D | pfpsp.S | 2039 # exception was being traced. Make the "current" PC the FPIAR and put it in the
|
| H A D | fpsp.S | 2040 # exception was being traced. Make the "current" PC the FPIAR and put it in the 4357 # remember, also, this instruction may be traced.
|