| /linux-4.4.14/tools/testing/fault-injection/ | 
| D | failcmd.sh | 42 	--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/ | 
| D | stacktrace.c | 90 stacktrace(void)  in stacktrace()  function 93 	instr * prologue = (instr *)stacktrace;  in stacktrace()
  | 
| /linux-4.4.14/arch/cris/kernel/ | 
| D | Makefile | 11 obj-y += stacktrace.o
  | 
| /linux-4.4.14/Documentation/fault-injection/ | 
| D | fault-injection.txt | 90 	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/ | 
| D | events.txt | 418 - 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 …] 
 | 
| D | ftrace.txt | 799   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/ | 
| D | Makefile | 14 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/hexagon/kernel/ | 
| D | Makefile | 17 obj-$(CONFIG_STACKTRACE) += stacktrace.o
  | 
| /linux-4.4.14/arch/unicore32/kernel/ | 
| D | Makefile | 7 obj-y				+= setup.o signal.o sys.o stacktrace.o traps.o
  | 
| /linux-4.4.14/arch/microblaze/kernel/ | 
| D | Makefile | 28 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/xtensa/kernel/ | 
| D | Makefile | 8 	 ptrace.o setup.o signal.o stacktrace.o syscall.o time.o traps.o \
  | 
| /linux-4.4.14/arch/metag/kernel/ | 
| D | Makefile | 20 obj-y	+= stacktrace.o
  | 
| /linux-4.4.14/arch/um/kernel/ | 
| D | Makefile | 22 obj-$(CONFIG_STACKTRACE) += stacktrace.o
  | 
| /linux-4.4.14/arch/arc/kernel/ | 
| D | Makefile | 12 obj-y	+= signal.o traps.o sys.o troubleshoot.o stacktrace.o disasm.o clk.o
  | 
| /linux-4.4.14/arch/blackfin/kernel/ | 
| D | Makefile | 34 obj-$(CONFIG_STACKTRACE)             += stacktrace.o
  | 
| /linux-4.4.14/arch/parisc/kernel/ | 
| D | Makefile | 31 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
  | 
| /linux-4.4.14/arch/sh/kernel/ | 
| D | Makefile | 37 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/lib/ | 
| D | dma-debug.c | 83 	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()
  | 
| D | Kconfig.debug | 1549 	bool "stacktrace filter for fault-injection capabilities" 1555 	  Provide stacktrace filter for fault-injection capabilities
  | 
| /linux-4.4.14/arch/s390/kernel/ | 
| D | Makefile | 60 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/arm64/kernel/ | 
| D | Makefile | 16 			   sys.o stacktrace.o time.o traps.o io.o vdso.o	\
  | 
| /linux-4.4.14/arch/ia64/kernel/ | 
| D | Makefile | 36 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/arm/kernel/ | 
| D | Makefile | 21 		   stacktrace.o sys_arm.o time.o traps.o
  | 
| /linux-4.4.14/arch/sparc/kernel/ | 
| D | Makefile | 98 obj-$(CONFIG_STACKTRACE)     += stacktrace.o
  | 
| /linux-4.4.14/kernel/ | 
| D | Makefile | 36 obj-$(CONFIG_STACKTRACE) += stacktrace.o
  | 
| /linux-4.4.14/arch/x86/kernel/ | 
| D | Makefile | 53 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/mips/kernel/ | 
| D | Makefile | 32 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/arch/powerpc/kernel/ | 
| D | Makefile | 104 obj-$(CONFIG_STACKTRACE)	+= stacktrace.o
  | 
| /linux-4.4.14/Documentation/x86/ | 
| D | kernel-stacks | 103 The question about the '?' preceding function names in an x86 stacktrace
  | 
| /linux-4.4.14/kernel/trace/ | 
| D | Kconfig | 367 	  To enable the stack tracer on bootup, pass in 'stacktrace'
  | 
| /linux-4.4.14/Documentation/ | 
| D | DMA-API.txt | 621 The driver developer can find the driver and the device including a stacktrace
  | 
| D | kernel-parameters.txt | 3572 	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/ | 
| D | Debugging390.txt | 1612 you the stacktrace by hand below).
  |