aboutsummaryrefslogtreecommitdiff
path: root/hmp-commands.hx
diff options
context:
space:
mode:
authorAndreas Färber <afaerber@suse.de>2013-05-17 11:54:40 +0200
committerAndreas Färber <afaerber@suse.de>2013-06-11 18:16:36 +0200
commit2a78636bd204e389068d203473ec76558083b44b (patch)
treea5226743ac3703457d6917134b0fcdd9ce48e88a /hmp-commands.hx
parentc22d8e0448aecb48a91f3936419ad1b63fbb4a6a (diff)
downloadqemu-arm-2a78636bd204e389068d203473ec76558083b44b.tar.gz
dump: Drop qmp_dump_guest_memory() stub and build for all targets
qmp_dump_guest_memory() calls dump_init() and returns an Error when cpu_get_dump_info() returns an error, as done by the stub. So there is no need to have a stub for qmp_dump_guest_memory(). Enable the documentation of the always-present dump-guest-memory command. That way we can drop CONFIG_HAVE_CORE_DUMP and leave configure completely out of the picture for target CPU features. Signed-off-by: Andreas Färber <afaerber@suse.de>
Diffstat (limited to 'hmp-commands.hx')
-rw-r--r--hmp-commands.hx2
1 files changed, 0 insertions, 2 deletions
diff --git a/hmp-commands.hx b/hmp-commands.hx
index 396691a5d6..915b0d16fa 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -991,7 +991,6 @@ server will ask the spice/vnc client to automatically reconnect using the
new parameters (if specified) once the vm migration finished successfully.
ETEXI
-#if defined(CONFIG_HAVE_CORE_DUMP)
{
.name = "dump-guest-memory",
.args_type = "paging:-p,filename:F,begin:i?,length:i?",
@@ -1015,7 +1014,6 @@ gdb.
length: the memory size, in bytes. It's optional, and should be specified
with begin together.
ETEXI
-#endif
{
.name = "snapshot_blkdev",