From 783e9b4826b95e53e33c42db6b4bd7d89bdff147 Mon Sep 17 00:00:00 2001 From: Wen Congyang Date: Mon, 7 May 2012 12:10:47 +0800 Subject: introduce a new monitor command 'dump-guest-memory' to dump guest's memory The command's usage: dump-guest-memory [-p] protocol [begin] [length] The supported protocol can be file or fd: 1. file: the protocol starts with "file:", and the following string is the file's path. 2. fd: the protocol starts with "fd:", and the following string is the fd's name. Note: 1. If you want to use gdb to process the core, please specify -p option. The reason why the -p option is not default is: a. guest machine in a catastrophic state can have corrupted memory, which we cannot trust. b. The guest machine can be in read-mode even if paging is enabled. For example: the guest machine uses ACPI to sleep, and ACPI sleep state goes in real-mode. 2. If you don't want to dump all guest's memory, please specify the start physical address and the length. Signed-off-by: Wen Congyang Signed-off-by: Luiz Capitulino --- Makefile.target | 2 ++ 1 file changed, 2 insertions(+) (limited to 'Makefile.target') diff --git a/Makefile.target b/Makefile.target index cf05831456..c94abfd3a4 100644 --- a/Makefile.target +++ b/Makefile.target @@ -405,6 +405,8 @@ obj-y += $(addprefix ../, $(trace-obj-y)) endif # CONFIG_SOFTMMU +obj-y += dump.o + ifndef CONFIG_LINUX_USER ifndef CONFIG_BSD_USER # libcacard needs qemu-thread support, and besides is only needed by devices -- cgit v1.2.3