Home
last modified time | relevance | path

Searched refs:traced (Results 1 – 25 of 25) sorted by relevance

/Linux-v5.10/Documentation/trace/
Dftrace-uses.rst93 This is the instruction pointer of the function that is being traced.
98 the function being traced (where the call of the function occurred).
135 is also traced, ftrace will prevent the callback from being called
154 the traced function (have another function called instead of the
155 traced function), it requires setting this flag. This is what live
247 to be traced.
255 functions it finds to not be traced. This is a separate list from the
Dftrace.rst231 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 …]
Devents.rst15 Not all tracepoints can be traced using the event tracing system;
334 but just will not be traced, unless of course it's actually enabled.
384 That is, the tracepoint will be called, but just will not be traced.
389 traced when a read system call is entered, and the :1 at the end
395 The following trigger causes kmalloc events to stop being traced
868 Finally, the event won't be actually traced until it's 'closed',
Duprobetracer.rst171 And you can see the traced information via /sys/kernel/debug/tracing/trace.
Dkprobetrace.rst239 And you can see the traced information via /sys/kernel/debug/tracing/trace.
/Linux-v5.10/arch/s390/kernel/
Dmcount.S44 stg %r14,(__SF_GPRS+8*8)(%r15) # save traced function caller
/Linux-v5.10/Documentation/arm64/
Dlegacy_instructions.rst25 usage of emulated instruction is traced as well as rate limited
Dmemory-tagging-extension.rst166 - ``-EPERM`` - the specified process cannot be traced.
/Linux-v5.10/Documentation/input/devices/
Dappletouch.rst81 full tracing (each sample is being traced)::
/Linux-v5.10/arch/arc/kernel/
Dentry.S318 ; (ii) If signal is SIGTRAP/SIGSTOP, task is being traced thus
/Linux-v5.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-filter.txt32 Filters can be attached to traced events. They can be used to filter out various
/Linux-v5.10/tools/perf/Documentation/
Dperf-intel-pt.txt710 In per-thread mode an exact list of threads is traced. There is no inheritance.
714 option, or processes selected with -p or -u) are traced. Each cpu has its own
717 In workload-only mode, the workload is traced but with per-cpu buffers.
1050 PSB+ occurs while control flow is being traced.
Dperf-record.txt140 - 'filter': defines a region that will be traced.
/Linux-v5.10/Documentation/dev-tools/
Dkmemleak.rst85 friends are traced and the pointers, together with additional
/Linux-v5.10/Documentation/driver-api/usb/
Ddwc3.rst667 operations, both of which can be traced. Format is::
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-kernel-slab489 should be traced.
/Linux-v5.10/Documentation/livepatch/
Dlivepatch.rst426 - Only functions that can be traced could be patched.
/Linux-v5.10/kernel/trace/
DKconfig471 when the likelys and unlikelys are not being traced.
/Linux-v5.10/drivers/scsi/qla2xxx/
Dqla_target.c1021 bool traced = false; in qlt_free_session_done() local
1025 if (!traced) { in qlt_free_session_done()
1029 traced = true; in qlt_free_session_done()
/Linux-v5.10/Documentation/filesystems/
Dproc.rst242 T is traced or stopped)
330 uninterruptible wait, Z is zombie, T is traced or stopped)
/Linux-v5.10/arch/m68k/ifpsp060/src/
Dpfpsp.S2039 # exception was being traced. Make the "current" PC the FPIAR and put it in the
Dfpsp.S2040 # exception was being traced. Make the "current" PC the FPIAR and put it in the
4357 # remember, also, this instruction may be traced.
/Linux-v5.10/arch/arm64/
DKconfig1333 enabled, CP15 barrier usage is traced which can help
/Linux-v5.10/lib/
DKconfig.debug652 detector. The memory allocation/freeing is traced in a way
/Linux-v5.10/Documentation/admin-guide/
Dkernel-parameters.txt1387 [FTRACE] Limit the functions traced by the function
1400 [FTRACE] Limit the top level callers functions traced