summaryrefslogtreecommitdiffstats
path: root/mm/cma_debug.c
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2020-08-18 01:44:48 +0200
committerPaul E. McKenney <paulmck@kernel.org>2020-08-25 03:45:54 +0200
commitb67a91703a29b93f5b114052b0b8e0d84e717ad3 (patch)
treebffa50e9e165a4be7a8d03462960653d16a2786c /mm/cma_debug.c
parentrcutorture: Allow pointer leaks to test diagnostic code (diff)
downloadlinux-b67a91703a29b93f5b114052b0b8e0d84e717ad3.tar.xz
linux-b67a91703a29b93f5b114052b0b8e0d84e717ad3.zip
torture: Add gdb support
This commit adds a "--gdb" parameter to kvm.sh, which causes "CONFIG_DEBUG_INFO=y" to be added to the Kconfig options, "nokaslr" to be added to the boot parameters, and "-s -S" to be added to the qemu arguments. Furthermore, the scripting prints messages telling the user how to start up gdb for the run in question. Because of the interactive nature of gdb sessions, only one "--configs" scenario is permitted when "--gdb" is specified. For most torture types, this means that a "--configs" argument is required, and that argument must specify the single scenario of interest. The usual cautions about breakpoints and timing apply, for example, staring at your gdb prompt for too long will likely get you many complaints, including RCU CPU stall warnings. Omar Sandoval further suggests using gdb's "hbreak" command instead of the "break" command on systems supporting hardware breakpoints, and further using the "commands" option because the resulting non-interactive breakpoints are less likely to get you RCU CPU stall warnings. Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'mm/cma_debug.c')
0 files changed, 0 insertions, 0 deletions