/openbmc/linux/arch/parisc/kernel/ |
H A D | Makefile | 32 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
|
/openbmc/linux/arch/um/kernel/ |
H A D | Makefile | 27 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
/openbmc/linux/Documentation/mm/ |
H A D | page_owner.rst | 139 ./page_owner_sort <input> <output> --cull=stacktrace 173 st stacktrace stack trace of the page allocation 186 st stacktrace stack trace of the page allocation
|
/openbmc/linux/arch/loongarch/kernel/ |
H A D | Makefile | 48 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
/openbmc/linux/Documentation/fault-injection/ |
H A D | fault-injection.rst | 125 stacktrace walking. Failure is injected only if some caller 126 in the walked stacktrace lies within the required range, and 131 - /sys/kernel/debug/fail*/stacktrace-depth: 133 specifies the maximum stacktrace depth walked during search 417 echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
|
/openbmc/linux/arch/riscv/kernel/ |
H A D | Makefile | 58 obj-y += stacktrace.o
|
/openbmc/linux/arch/s390/kernel/ |
H A D | Makefile | 44 obj-y += smp.o text_amode31.o stacktrace.o abs_lowcore.o
|
/openbmc/linux/arch/arm64/kvm/hyp/nvhe/ |
H A D | Makefile | 25 cache.o setup.o mm.o mem_protect.o sys_regs.o pkvm.o stacktrace.o ffa.o
|
/openbmc/linux/Documentation/trace/ |
H A D | events.rst | 468 - stacktrace 470 This command dumps a stacktrace in the trace buffer whenever the 473 For example, the following trigger dumps a stacktrace every time the 476 # echo 'stacktrace' > \ 482 # echo 'stacktrace:5 if bytes_req >= 65536' > \ 487 stacktrace[:count] 491 # echo '!stacktrace' > \ 494 # echo '!stacktrace:5 if bytes_req >= 65536' > \ 500 # echo '!stacktrace:5' > \ 503 Note that there can be only one stacktrace trigger per triggering [all …]
|
H A D | timerlat-tracer.rst | 101 stacktrace section). Then the timer interrupt that wakes up the timerlat 137 IRQ stacktrace
|
H A D | histogram.rst | 20 event format fields (or stacktrace) and a set of running totals 39 will use the event's kernel stacktrace as the key. The keywords 84 .stacktrace display as a stacktrace (must by a long[] type) 1026 First we set up an initially paused stacktrace trigger on the 1038 hash table keyed on stacktrace:: 1993 A synthetic event that has a stacktrace field may use it as a key in 2003 { delta: ~ 0-99, stack.stacktrace __schedule+0xa19/0x1520 2015 { delta: ~ 0-99, stack.stacktrace __schedule+0xa19/0x1520 2031 { delta: ~ 0-99, stack.stacktrace __schedule+0xa19/0x1520 2047 { delta: ~ 0-99, stack.stacktrace __schedule+0xa19/0x1520 [all …]
|
H A D | ftrace.rst | 1173 stacktrace of the current user space thread after 1177 when user stacktrace are enabled, look up which 1290 stacktrace 3351 - stacktrace: 3694 the stack size of the kernel during boot up, by adding "stacktrace"
|
/openbmc/linux/arch/arm64/kernel/ |
H A D | Makefile | 31 setup.o signal.o sys.o stacktrace.o time.o traps.o \
|
/openbmc/linux/arch/arm/kernel/ |
H A D | Makefile | 23 stacktrace.o sys_arm.o time.o traps.o
|
/openbmc/linux/arch/sparc/kernel/ |
H A D | Makefile | 100 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
/openbmc/linux/arch/mips/kernel/ |
H A D | Makefile | 39 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
/openbmc/linux/arch/x86/kernel/ |
H A D | Makefile | 77 obj-y += stacktrace.o
|
/openbmc/linux/kernel/ |
H A D | Makefile | 58 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-dbs/mongodb/ |
H A D | mongodb_git.bb | 28 file://0001-stacktrace-Define-ARCH_BITS-for-x86.patch \
|
/openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
H A D | kasan.rst | 113 - ``kasan.stacktrace=off`` 或 ``=on`` 禁用或启用分配和释放堆栈痕
|
/openbmc/linux/arch/powerpc/kernel/ |
H A D | Makefile | 79 kdebugfs.o stacktrace.o syscall.o
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | kernel-stacks.rst | 114 The question about the '?' preceding function names in an x86 stacktrace
|
/openbmc/openbmc/poky/bitbake/ |
H A D | ChangeLog | 88 - Don't give a stacktrace for invalid tasks, have a user friendly message (#3431)
|
/openbmc/linux/kernel/trace/ |
H A D | Kconfig | 332 To enable the stack tracer on bootup, pass in 'stacktrace' 500 stacktrace at the IRQ context, which helps to identify the code
|
/openbmc/linux/arch/ |
H A D | Kconfig | 230 stacktrace may see the kretprobe trampoline address instead 231 of correct one. If the architecture stacktrace code and
|