Searched refs:stacktrace (Results 1 – 25 of 39) sorted by relevance
12
| /Linux-v5.15/tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-stacktrace.tc | 11 FEATURE=`grep stacktrace events/sched/sched_process_fork/trigger`
19 echo 0 > options/stacktrace
|
| /Linux-v5.15/tools/testing/fault-injection/ |
| D | failcmd.sh | 43 --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.15/arch/csky/kernel/ |
| D | Makefile | 6 obj-y += process.o cpu-probe.o ptrace.o stacktrace.o
12 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/alpha/lib/ |
| D | stacktrace.c | 91 stacktrace(void) in stacktrace() function
94 instr * prologue = (instr *)stacktrace; in stacktrace()
|
| /Linux-v5.15/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | func-filter-stacktrace.tc | 7 echo $FUNCTION_FORK:stacktrace >> set_ftrace_filter
|
| /Linux-v5.15/Documentation/livepatch/ |
| D | index.rst | 16 reliable-stacktrace
|
| D | reliable-stacktrace.rst | 16 to identify which functions are live is to use a stacktrace.
18 Existing stacktrace code may not always give an accurate picture of all
21 to provide a *reliable* stacktrace which ensures it never omits any live
28 Architectures must implement one of the reliable stacktrace functions.
33 Principally, the reliable stacktrace function must ensure that either:
45 Secondly, the reliable stacktrace function must be robust to cases where
89 architectures verify that a stacktrace ends at an expected location, e.g.
|
| /Linux-v5.15/arch/openrisc/kernel/ |
| D | Makefile | 13 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/tools/testing/ktest/examples/bootconfigs/ |
| D | tracing.bconf | 3 options = event-fork, sym-addr, stacktrace;
|
| /Linux-v5.15/arch/hexagon/kernel/ |
| D | Makefile | 18 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/microblaze/kernel/ |
| D | Makefile | 26 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/xtensa/kernel/ |
| D | Makefile | 9 ptrace.o setup.o signal.o stacktrace.o syscall.o time.o traps.o \
|
| /Linux-v5.15/arch/nds32/kernel/ |
| D | Makefile | 16 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/arc/kernel/ |
| D | Makefile | 7 obj-y += signal.o traps.o sys.o troubleshoot.o stacktrace.o disasm.o
|
| /Linux-v5.15/arch/parisc/kernel/ |
| D | Makefile | 29 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
|
| /Linux-v5.15/arch/sh/kernel/ |
| D | Makefile | 38 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/um/kernel/ |
| D | Makefile | 25 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/Documentation/trace/ |
| D | histogram.rst | 20 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
541 value 'stacktrace' for the key parameter::
543 # echo 'hist:keys=stacktrace:values=bytes_req,bytes_alloc:sort=bytes_alloc' > \
555 …# trigger info: hist:keys=stacktrace:vals=bytes_req,bytes_alloc:sort=bytes_alloc:size=2048 [active]
557 { stacktrace:
575 { stacktrace:
590 { stacktrace:
[all …]
|
| D | events.rst | 423 - 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 …]
|
| D | timerlat-tracer.rst | 100 stacktrace section). Then the timer interrupt that wakes up the timerlat
136 IRQ stacktrace
|
| /Linux-v5.15/arch/ia64/kernel/ |
| D | Makefile | 35 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/riscv/kernel/ |
| D | Makefile | 35 obj-y += stacktrace.o
|
| /Linux-v5.15/Documentation/fault-injection/ |
| D | fault-injection.rst | 119 stacktrace walking. Failure is injected only if some caller
120 in the walked stacktrace lies within the required range, and
125 - /sys/kernel/debug/fail*/stacktrace-depth:
127 specifies the maximum stacktrace depth walked during search
339 echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
|
| /Linux-v5.15/arch/s390/kernel/ |
| D | Makefile | 58 obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
| /Linux-v5.15/arch/arm64/kernel/ |
| D | Makefile | 26 setup.o signal.o sys.o stacktrace.o time.o traps.o \
|
12
