Home
last modified time | relevance | path

Searched refs:traces (Results 76 – 100 of 103) sorted by relevance

12345

/openbmc/openbmc/poky/meta/recipes-core/glibc/
H A Dglibc-package.inc65 DESCRIPTION:libsotruss = "Library to support sotruss which traces calls through PLTs"
/openbmc/linux/arch/arm64/boot/dts/ti/
H A Dk3-am642-tqma64xxl-mbax4xxl.dts248 * Note: We expect usage of a SYSFW that does not reserve UART1 for debug traces
/openbmc/linux/Documentation/livepatch/
H A Dreliable-stacktrace.rst263 assumption can lead to unreliable stack traces. For example, consider the
/openbmc/linux/Documentation/trace/
H A Dftrace.rst155 or events work (stack traces, timestamps, etc).
772 whereas the function graph tracer traces on both entry
799 Similar to irqsoff but traces and records the amount of
804 Similar to irqsoff and preemptoff, but traces and
1094 On function traces, display the calling (parent)
1611 The preemptoff tracer traces the places that disable preemption.
1968 The tracer only traces the highest priority task in the system
/openbmc/linux/Documentation/dev-tools/
H A Dkcsan.rst52 the race. It is followed by the access types and stack traces of the 2 threads
H A Dkgdb.rst68 more accurately construct stack back traces while debugging the kernel.
/openbmc/linux/Documentation/filesystems/caching/
H A Dbackend-api.rst31 to make it easier to correlate traces. Note, though, that debugging IDs are
/openbmc/linux/Documentation/userspace-api/
H A Dseccomp_filter.rst286 memory is accessible to suitably privileged traces via ``ptrace()`` or
/openbmc/linux/kernel/trace/
H A DKconfig508 Mmiotrace traces Memory Mapped I/O access and is meant for
634 This traces the events of likely and unlikely condition
/openbmc/openbmc/poky/documentation/ref-manual/
H A Dfeatures.rst165 …to binary files containing, allowing ``coredumpctl`` and ``gdb`` to show symbolicated stack traces.
/openbmc/linux/Documentation/admin-guide/
H A Dworkload-tracing.rst302 traces for the paxtest kiddie run to see which function is calling other
/openbmc/linux/Documentation/hid/
H A Dhid-bpf.rst311 (where it is interesting to get the non-hidraw traces).
/openbmc/linux/tools/perf/Documentation/
H A Dperf-intel-pt.txt116 perf script also supports higher level ways to dump instruction traces:
643 Full-trace mode traces continuously e.g.
1299 Intel PT traces both the host and the guest so --guest and --host need to be specified.
1362 Intel PT traces both the host and the guest so --guest and --host need to be specified.
H A Dperf-record.txt820 Note that BPF can collect stack traces using frame pointer ("fp")
/openbmc/qemu/docs/devel/
H A Dtcg-plugins.rst471 The execlog tool traces executed instructions with memory access. It can be used
/openbmc/linux/Documentation/networking/
H A Dphy.rst84 or the PCB traces insert the correct 1.5-2ns delay
/openbmc/linux/arch/arm/
H A DKconfig.debug54 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
64 kernel stack traces.
/openbmc/qemu/target/hexagon/idef-parser/
H A DREADME.rst498 And do the same for your implementation, the generated execution traces will be
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dpopulate_sdk_ext.bbclass128 """Clean up traces of the fake build for create_filtered_tasklist()"""
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A Dspectre.rst54 traces of memory accesses or computations in the processor's caches,
/openbmc/linux/lib/
H A DKconfig.debug549 runtime stack traces are more reliable.
1570 and relevant stack traces.
/openbmc/linux/Documentation/RCU/Design/Data-Structures/
H A DData-Structures.rst371 result in confusing traces, but better some tracing confusion than to be
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst296 the console. This is very useful for capturing traces that lead to
/openbmc/u-boot/cmd/
H A DKconfig1916 U-Boot. This allows recording of call traces including timing
/openbmc/openbmc/poky/meta/classes-global/
H A Dinsane.bbclass19 # -Check if config.log contains traces to broken autoconf tests

12345