From: Wen Congyang <wency@cn.fujitsu.com>
To: qemu-devel <qemu-devel@nongnu.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Dave Anderson <anderson@redhat.com>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Eric Blake <eblake@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 12/12 v11] introduce a new monitor command 'dump-guest-memory' to dump guest's memory
Date: Mon, 02 Apr 2012 10:54:11 +0800 [thread overview]
Message-ID: <4F7914D3.3070703@cn.fujitsu.com> (raw)
In-Reply-To: <4F703FB0.6070109@cn.fujitsu.com>
At 03/26/2012 06:06 PM, Wen Congyang Wrote:
> The command's usage:
> dump [-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. This command doesn't support the fd that is is associated with a pipe,
> socket, or FIFO(lseek will fail with such fd).
> 3. 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 <wency@cn.fujitsu.com>
> ---
> Makefile.target | 2 +-
> dump.c | 827 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> elf.h | 5 +
> hmp-commands.hx | 28 ++
> hmp.c | 22 ++
> hmp.h | 1 +
> memory_mapping.c | 27 ++
> memory_mapping.h | 3 +
> qapi-schema.json | 34 +++
> qmp-commands.hx | 38 +++
> 10 files changed, 986 insertions(+), 1 deletions(-)
> create mode 100644 dump.c
<cut>
> +/* write the memroy to vmcore. 1 page per I/O. */
> +static int write_memory(DumpState *s, RAMBlock *block, ram_addr_t start,
> + target_phys_addr_t *offset, int64_t size)
> +{
> + int i, ret;
The type of i should be int64_t. Otherwise, i * TARGET_PAGE_SIZE
may be overflow.
I will resend this patch.
Thanks
Wen Congyang
> +
> + for (i = 0; i < size / TARGET_PAGE_SIZE; i++) {
> + ret = write_data(s, block->host + start + i * TARGET_PAGE_SIZE,
> + TARGET_PAGE_SIZE, offset);
> + if (ret < 0) {
> + return ret;
> + }
> + }
> +
> + if ((size % TARGET_PAGE_SIZE) != 0) {
> + ret = write_data(s, block->host + start + i * TARGET_PAGE_SIZE,
> + size % TARGET_PAGE_SIZE, offset);
> + if (ret < 0) {
> + return ret;
> + }
> + }
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2012-04-02 3:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 9:58 [Qemu-devel] [PATCH 00/12 v11] introducing a new, dedicated guest memory dump mechanism Wen Congyang
2012-03-26 10:00 ` [Qemu-devel] [PATCH 01/12 v11] Add API to create memory mapping list Wen Congyang
2012-03-26 10:01 ` [Qemu-devel] [PATCH 02/12 v12] Add API to check whether a physical address is I/O address Wen Congyang
2012-03-26 10:02 ` [Qemu-devel] [PATCH 03/12 v11] implement cpu_get_memory_mapping() Wen Congyang
2012-03-26 10:02 ` [Qemu-devel] [PATCH 04/12 v11] Add API to check whether paging mode is enabled Wen Congyang
2012-03-26 10:03 ` [Qemu-devel] [PATCH 05/12 v11] Add API to get memory mapping Wen Congyang
2012-03-27 2:27 ` Wen Congyang
2012-03-26 10:03 ` [Qemu-devel] [PATCH 06/12 v11] Add API to get memory mapping without do paging Wen Congyang
2012-03-26 10:04 ` [Qemu-devel] [PATCH 07/12 v11] target-i386: Add API to write elf notes to core file Wen Congyang
2012-03-26 10:04 ` [Qemu-devel] [PATCH 08/12 v11] target-i386: Add API to write cpu status " Wen Congyang
2012-03-26 10:05 ` [Qemu-devel] [PATCH 09/12 v11] target-i386: add API to get dump info Wen Congyang
2012-03-26 10:05 ` [Qemu-devel] [PATCH 10/12 v11] make gdb_id() generally avialable and rename it to cpu_index() Wen Congyang
2012-03-27 3:38 ` HATAYAMA Daisuke
2012-03-26 10:06 ` [Qemu-devel] [PATCH 11/12 v11] QError: Introduce new error for the dump-guest-memory command Wen Congyang
2012-03-26 10:06 ` [Qemu-devel] [PATCH 12/12 v11] introduce a new monitor command 'dump-guest-memory' to dump guest's memory Wen Congyang
2012-04-02 2:54 ` Wen Congyang [this message]
2012-04-02 3:16 ` [Qemu-devel] [PATCH 12/12 v11.5] " Wen Congyang
2012-03-28 5:17 ` [Qemu-devel] [PATCH 00/12 v11] introducing a new, dedicated guest memory dump mechanism Wen Congyang
2012-03-28 12:44 ` Luiz Capitulino
2012-04-02 3:19 ` Wen Congyang
2012-04-03 7:35 ` Jan Kiszka
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=4F7914D3.3070703@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=aliguori@us.ibm.com \
--cc=anderson@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=eblake@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).