From: Eric Blake <eblake@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Dave Anderson <anderson@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH 8/8 v3] introduce a new monitor command 'dump' to dump guest's memory
Date: Tue, 20 Dec 2011 09:25:53 -0700 [thread overview]
Message-ID: <4EF0B711.6070909@redhat.com> (raw)
In-Reply-To: <4EF0522D.4040906@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On 12/20/2011 02:15 AM, Wen Congyang wrote:
> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> ---
> Makefile.target | 8 +-
> dump.c | 452 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> dump.h | 4 +
> hmp-commands.hx | 16 ++
> monitor.c | 3 +
> qmp-commands.hx | 24 +++
> 6 files changed, 503 insertions(+), 4 deletions(-)
> create mode 100644 dump.c
>
> +++ b/qmp-commands.hx
> @@ -469,6 +469,30 @@ Notes:
> EQMP
>
> {
> + .name = "dump",
> + .args_type = "file:s",
> + .params = "file",
> + .help = "dump to file",
> + .user_print = monitor_user_noop,
> + .mhandler.cmd_new = do_dump,
> + },
From a libvirt perspective, we would like the option to be able to pass
in an already-open fd rather than just a file name. This is possible if
the 'file' argument is required to start with '/' for an absolute path,
vs. 'file:name' for an fd previously passed in via the getfd monitor
command.
Also, does this command block? It sounds like it is long-running, which
means it probably needs to be asynchronous, as well as issue an event
upon completion, so that other monitor commands can be issued in the
meantime.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2011-12-20 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 8:54 [Qemu-devel] [RFC][PATCT 0/8 v3] dump memory when host pci device is used by guest Wen Congyang
2011-12-20 9:07 ` [Qemu-devel] [RFC][PATCH 1/8 v3] Add API to create memory mapping list Wen Congyang
2011-12-20 9:09 ` [Qemu-devel] [RFC][PATCH 2/8 v3] Add API to check whether a physical address is I/O address Wen Congyang
2011-12-20 9:10 ` [Qemu-devel] [RFC][PATCH 3/8 v3] target-i386: implement cpu_get_memory_mapping() Wen Congyang
2011-12-20 9:11 ` [Qemu-devel] [RFC][PATCH 4/8 v3] Add API to get memory mapping Wen Congyang
2011-12-20 9:12 ` [Qemu-devel] [RFC][PATCH 5/8 v3] target-i386: Add API to write elf notes to core file Wen Congyang
2011-12-20 9:13 ` [Qemu-devel] [RFC][PATCH 6/8 v3] target-i386: Add API to add extra memory mapping Wen Congyang
2011-12-20 9:14 ` [Qemu-devel] [RFC][PATCH 7/8 v3] target-i386: add API to get dump info Wen Congyang
2011-12-20 9:15 ` [Qemu-devel] [RFC][PATCH 8/8 v3] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2011-12-20 16:25 ` Eric Blake [this message]
2011-12-21 1:10 ` Wen Congyang
2011-12-21 2:42 ` andrzej zaborowski
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=4EF0B711.6070909@redhat.com \
--to=eblake@redhat.com \
--cc=anderson@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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).