Home
last modified time | relevance | path

Searched refs:traces (Results 26 – 50 of 103) sorted by relevance

12345

/openbmc/linux/Documentation/usb/
H A Dusbmon.rst9 used to collect traces of I/O on the USB bus. This function is analogous
12 USBMon (with uppercase letters) is used to examine raw traces produced
16 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
24 How to use usbmon to collect raw text traces
27 Unlike the packet socket, usbmon has an interface which provides traces
/openbmc/linux/arch/arm64/boot/dts/freescale/
H A Dimx8mm-verdin-dev.dtsi156 /* Limit frequency on dev board due to long traces and bad signal integrity */
H A Dimx8mp-verdin-dev.dtsi208 /* Limit frequency on dev board due to long traces and bad signal integrity */
/openbmc/linux/Documentation/filesystems/caching/
H A Dfscache.rst241 CACHE Cache cookie debug ID (also appears in traces)
271 VOLUME The volume cookie debug ID (also appears in traces)
307 COOKIE The cookie debug ID (also appears in traces)
/openbmc/linux/Documentation/networking/device_drivers/atm/
H A Diphase.rst128 IADebugFlag, which controls the output of the traces. You can find the bit
132 traces together with loading the driver.
/openbmc/linux/Documentation/trace/coresight/
H A Dcoresight-perf.rst93 are in tests/shell/coresight and will collect traces to ensure a
130 quality of traces.
/openbmc/linux/Documentation/core-api/irq/
H A Dirqflags-tracing.rst7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
/openbmc/linux/Documentation/trace/
H A Dintel_th.rst96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
/openbmc/linux/drivers/of/
H A DKconfig29 traces to print on the console. It is possible that the tests will
/openbmc/linux/drivers/hwtracing/intel_th/
H A DKconfig65 storing STP traces to system memory. It supports single
/openbmc/linux/net/batman-adv/
H A DKconfig93 say N here. Select this option to gather traces like the debug
/openbmc/linux/include/linux/
H A Dremoteproc.h562 struct list_head traces; member
/openbmc/linux/arch/arm/boot/dts/nxp/ls/
H A Dls1021a-tsn.dts121 /* RGMII delays added via PCB traces */
/openbmc/linux/Documentation/dev-tools/
H A Dkasan.rst93 To include alloc and free stack traces of affected slab objects into reports,
94 enable ``CONFIG_STACKTRACE``. To include alloc and free stack traces of affected
121 traces collection (default: ``on``).
272 Generic KASAN also reports up to two auxiliary call stack traces. These stack
273 traces point to places in code that interacted with the object but that are not
/openbmc/qemu/docs/devel/
H A Dtracing.rst53 traces in the simpletrace data format.
311 enable/disable, and dump traces.
347 babeltrace $HOME/lttng-traces/mysession-<date>-<time>
/openbmc/linux/Documentation/mm/
H A Dslub.rst399 Prints information about unique allocation traces of the currently
430 Prints information about unique freeing traces of the currently allocated
431 objects. The freeing traces thus come from the previous life-cycle of the
/openbmc/linux/arch/powerpc/
H A DKconfig.debug24 prints in stack traces. This can be useful if your display is
25 too small and stack traces cause important information to
/openbmc/linux/Documentation/RCU/
H A Dstallwarn.rst123 To diagnose the cause of the stall, inspect the stack traces.
126 comparing the stack traces can often help determine where the stall
199 own warnings, as this often gives better-quality stack traces.
346 involved in the stall. These stack traces can help you locate the cause
/openbmc/u-boot/arch/arm/dts/
H A Dsun8i-a83t-allwinner-h8homlet-v2.dts221 * Set a 100ms delay to account for PMIC ramp time and board traces.
H A Dsun8i-a83t-bananapi-m3.dts341 * ramp time and board traces.
/openbmc/linux/arch/arm/boot/dts/allwinner/
H A Dsun8i-a83t-allwinner-h8homlet-v2.dts233 * Set a 100ms delay to account for PMIC ramp time and board traces.
/openbmc/linux/tools/perf/Documentation/
H A Dperf-script.txt446 for intel_pt traces. The default is 'raw'. To use xed, combine
484 Show call stream for intel_pt traces. The CPUs are interleaved, but
488 Show call and return stream for intel_pt traces.
/openbmc/linux/drivers/remoteproc/
H A Dremoteproc_core.c581 list_add_tail(&trace->node, &rproc->traces); in rproc_handle_trace()
1228 list_for_each_entry_safe(trace, ttmp, &rproc->traces, node) { in rproc_resource_cleanup()
2493 INIT_LIST_HEAD(&rproc->traces); in rproc_alloc()
/openbmc/openbmc/poky/scripts/pybootchartgui/
H A DNEWS112 + handle empty traces more elegantly
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/breakpad/
H A Dbreakpad_2023.06.01.bb6 …dump\" files, send them back to your server, and produce C and C++ stack traces from these minidum…

12345