Home
last modified time | relevance | path

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

/linux-4.4.14/tools/testing/fault-injection/
Dfailcmd.sh42 --stacktrace-depth=value, --require-start=value, --require-end=value,
87 LONGOPTS=$LONGOPTS,stacktrace-depth:,require-start:,require-end:
157 --stacktrace-depth)
158 echo $2 > $FAULTATTR/stacktrace-depth
/linux-4.4.14/arch/alpha/lib/
Dstacktrace.c90 stacktrace(void) in stacktrace() function
93 instr * prologue = (instr *)stacktrace; in stacktrace()
/linux-4.4.14/arch/cris/kernel/
DMakefile11 obj-y += stacktrace.o
/linux-4.4.14/Documentation/fault-injection/
Dfault-injection.txt90 stacktrace walking. Failure is injected only if some caller
91 in the walked stacktrace lies within the required range, and
96 - /sys/kernel/debug/fail*/stacktrace-depth:
98 specifies the maximum stacktrace depth walked during search
247 echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
/linux-4.4.14/Documentation/trace/
Devents.txt418 - stacktrace
420 This command dumps a stacktrace in the trace buffer whenever the
423 For example, the following trigger dumps a stacktrace every time the
426 # echo 'stacktrace' > \
429 The following trigger dumps a stacktrace the first 5 times a kmalloc
432 # echo 'stacktrace:5 if bytes_req >= 65536' > \
437 stacktrace[:count]
441 # echo '!stacktrace' > \
444 # echo '!stacktrace:5 if bytes_req >= 65536' > \
450 # echo '!stacktrace:5' > \
[all …]
Dftrace.txt799 stacktrace - This is one of the options that changes the trace
826 stacktrace of the current userspace thread.
828 sym-userobj - when user stacktrace are enabled, look up which
2860 the stack size of the kernel during boot up, by adding "stacktrace"
/linux-4.4.14/arch/avr32/kernel/
DMakefile14 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/hexagon/kernel/
DMakefile17 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/unicore32/kernel/
DMakefile7 obj-y += setup.o signal.o sys.o stacktrace.o traps.o
/linux-4.4.14/arch/microblaze/kernel/
DMakefile28 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/xtensa/kernel/
DMakefile8 ptrace.o setup.o signal.o stacktrace.o syscall.o time.o traps.o \
/linux-4.4.14/arch/metag/kernel/
DMakefile20 obj-y += stacktrace.o
/linux-4.4.14/arch/um/kernel/
DMakefile22 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/arc/kernel/
DMakefile12 obj-y += signal.o traps.o sys.o troubleshoot.o stacktrace.o disasm.o clk.o
/linux-4.4.14/arch/blackfin/kernel/
DMakefile34 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/parisc/kernel/
DMakefile31 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
/linux-4.4.14/arch/sh/kernel/
DMakefile37 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/lib/
Ddma-debug.c83 struct stack_trace stacktrace; member
177 print_stack_trace(&entry->stacktrace, 0); in dump_entry_trace()
671 entry->stacktrace.max_entries = DMA_DEBUG_STACKTRACE_ENTRIES; in dma_entry_alloc()
672 entry->stacktrace.entries = entry->st_entries; in dma_entry_alloc()
673 entry->stacktrace.skip = 2; in dma_entry_alloc()
674 save_stack_trace(&entry->stacktrace); in dma_entry_alloc()
DKconfig.debug1549 bool "stacktrace filter for fault-injection capabilities"
1555 Provide stacktrace filter for fault-injection capabilities
/linux-4.4.14/arch/s390/kernel/
DMakefile60 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/arm64/kernel/
DMakefile16 sys.o stacktrace.o time.o traps.o io.o vdso.o \
/linux-4.4.14/arch/ia64/kernel/
DMakefile36 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/arm/kernel/
DMakefile21 stacktrace.o sys_arm.o time.o traps.o
/linux-4.4.14/arch/sparc/kernel/
DMakefile98 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/kernel/
DMakefile36 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/x86/kernel/
DMakefile53 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/mips/kernel/
DMakefile32 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/arch/powerpc/kernel/
DMakefile104 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux-4.4.14/Documentation/x86/
Dkernel-stacks103 The question about the '?' preceding function names in an x86 stacktrace
/linux-4.4.14/kernel/trace/
DKconfig367 To enable the stack tracer on bootup, pass in 'stacktrace'
/linux-4.4.14/Documentation/
DDMA-API.txt621 The driver developer can find the driver and the device including a stacktrace
Dkernel-parameters.txt3572 stacktrace [FTRACE]
3581 and the stacktrace above is not needed.
3779 For example, to enable stacktrace option (to dump the
3782 trace_options=stacktrace
/linux-4.4.14/Documentation/s390/
DDebugging390.txt1612 you the stacktrace by hand below).