Home
last modified time | relevance | path

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

12

/Linux-v5.10/tools/testing/selftests/ftrace/test.d/trigger/
Dtrigger-stacktrace.tc11 FEATURE=`grep stacktrace events/sched/sched_process_fork/trigger`
19 echo 0 > options/stacktrace
/Linux-v5.10/tools/testing/fault-injection/
Dfailcmd.sh43 --stacktrace-depth=value, --require-start=value, --require-end=value,
88 LONGOPTS=$LONGOPTS,stacktrace-depth:,require-start:,require-end:
158 --stacktrace-depth)
159 echo $2 > $FAULTATTR/stacktrace-depth
/Linux-v5.10/arch/csky/kernel/
DMakefile6 obj-y += process.o cpu-probe.o ptrace.o stacktrace.o
12 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/alpha/lib/
Dstacktrace.c91 stacktrace(void) in stacktrace() function
94 instr * prologue = (instr *)stacktrace; in stacktrace()
/Linux-v5.10/tools/testing/selftests/ftrace/test.d/ftrace/
Dfunc-filter-stacktrace.tc7 echo $FUNCTION_FORK:stacktrace >> set_ftrace_filter
/Linux-v5.10/arch/openrisc/kernel/
DMakefile13 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/hexagon/kernel/
DMakefile18 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/microblaze/kernel/
DMakefile26 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/xtensa/kernel/
DMakefile9 ptrace.o setup.o signal.o stacktrace.o syscall.o time.o traps.o \
/Linux-v5.10/arch/nds32/kernel/
DMakefile16 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/um/kernel/
DMakefile26 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/arc/kernel/
DMakefile7 obj-y += signal.o traps.o sys.o troubleshoot.o stacktrace.o disasm.o
/Linux-v5.10/arch/sh/kernel/
DMakefile38 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/riscv/kernel/
DMakefile29 obj-y += stacktrace.o
/Linux-v5.10/arch/parisc/kernel/
DMakefile29 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
/Linux-v5.10/Documentation/fault-injection/
Dfault-injection.rst113 stacktrace walking. Failure is injected only if some caller
114 in the walked stacktrace lies within the required range, and
119 - /sys/kernel/debug/fail*/stacktrace-depth:
121 specifies the maximum stacktrace depth walked during search
317 echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
/Linux-v5.10/Documentation/trace/
Dhistogram.rst20 event format fields (or stacktrace) and a set of running totals
38 Keys can be any field, or the special string 'stacktrace', which
39 will use the event's kernel stacktrace as the key. The keywords
57 'stacktrace' fields and can therefore be combined using those
540 value 'stacktrace' for the key parameter::
542 # echo 'hist:keys=stacktrace:values=bytes_req,bytes_alloc:sort=bytes_alloc' > \
554 …# trigger info: hist:keys=stacktrace:vals=bytes_req,bytes_alloc:sort=bytes_alloc:size=2048 [active]
556 { stacktrace:
574 { stacktrace:
589 { stacktrace:
[all …]
Devents.rst423 - stacktrace
425 This command dumps a stacktrace in the trace buffer whenever the
428 For example, the following trigger dumps a stacktrace every time the
431 # echo 'stacktrace' > \
434 The following trigger dumps a stacktrace the first 5 times a kmalloc
437 # echo 'stacktrace:5 if bytes_req >= 65536' > \
442 stacktrace[:count]
446 # echo '!stacktrace' > \
449 # echo '!stacktrace:5 if bytes_req >= 65536' > \
455 # echo '!stacktrace:5' > \
[all …]
/Linux-v5.10/arch/ia64/kernel/
DMakefile35 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/arm64/kernel/
DMakefile15 setup.o signal.o sys.o stacktrace.o time.o traps.o \
/Linux-v5.10/arch/s390/kernel/
DMakefile58 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/arm/kernel/
DMakefile22 stacktrace.o sys_arm.o time.o traps.o
/Linux-v5.10/arch/sparc/kernel/
DMakefile100 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/arch/mips/kernel/
DMakefile39 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/Linux-v5.10/kernel/
DMakefile54 obj-$(CONFIG_STACKTRACE) += stacktrace.o

12