From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, imammedo@redhat.com,
sjitindarsingh@gmail.com, walling@linux.ibm.com
Cc: armbru@redhat.com
Subject: [Qemu-devel] [PULL 2/9] hmp-commands: use long for begin and length in dump-guest-memory
Date: Thu, 21 Jun 2018 17:47:20 +0100 [thread overview]
Message-ID: <20180621164727.36626-3-dgilbert@redhat.com> (raw)
In-Reply-To: <20180621164727.36626-1-dgilbert@redhat.com>
From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
The dump-guest-memory command is used to dump an area of guest memory
to a file, the piece of memory is specified by a begin address and
a length. These parameters are specified as ints and thus have a maximum
value of 4GB. This means you can't dump the guest memory past the first
4GB and instead get:
(qemu) dump-guest-memory tmp 0x100000000 0x100000000
'dump-guest-memory' has failed: integer is for 32-bit values
Try "help dump-guest-memory" for more information
This limitation is imposed in monitor_parse_arguments() since they are
both ints. hmp_dump_guest_memory() uses 64 bit quantities to store both
the begin and length values. Thus specify begin and length as long so
that the entire guest memory space can be dumped.
Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Message-Id: <20180620003202.10546-1-sjitindarsingh@gmail.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
---
hmp-commands.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hmp-commands.hx b/hmp-commands.hx
index 0de7c4c29e..754620e411 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -1116,7 +1116,7 @@ ETEXI
{
.name = "dump-guest-memory",
- .args_type = "paging:-p,detach:-d,zlib:-z,lzo:-l,snappy:-s,filename:F,begin:i?,length:i?",
+ .args_type = "paging:-p,detach:-d,zlib:-z,lzo:-l,snappy:-s,filename:F,begin:l?,length:l?",
.params = "[-p] [-d] [-z|-l|-s] filename [begin length]",
.help = "dump guest memory into file 'filename'.\n\t\t\t"
"-p: do paging to get guest's memory mapping.\n\t\t\t"
--
2.17.1
next prev parent reply other threads:[~2018-06-21 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:47 [Qemu-devel] [PULL 0/9] hmp queue Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 1/9] monitor: report entirety of hmp command on error Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` Dr. David Alan Gilbert (git) [this message]
2018-06-21 16:47 ` [Qemu-devel] [PULL 3/9] hmp: Add flag for preconfig commands Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 4/9] hmp: Allow help on " Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 5/9] hmp: Restrict auto-complete in preconfig Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 6/9] qmp: Enable a few commands in preconfig state Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 7/9] hmp: Add commands for preconfig Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 8/9] hmp: add exit_preconfig Dr. David Alan Gilbert (git)
2018-06-21 16:47 ` [Qemu-devel] [PULL 9/9] hmp: Allow HMP in preconfig state again Dr. David Alan Gilbert (git)
2018-06-22 13:18 ` [Qemu-devel] [PULL 0/9] hmp queue Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180621164727.36626-3-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sjitindarsingh@gmail.com \
--cc=walling@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).