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>
Subject: Re: [Qemu-devel] [RFC][PATCH 00/16 v6] introducing a new, dedicated memory dump mechanism
Date: Mon, 13 Feb 2012 09:45:25 +0800 [thread overview]
Message-ID: <4F386B35.8050508@cn.fujitsu.com> (raw)
In-Reply-To: <4F333AAA.1070601@cn.fujitsu.com>
At 02/09/2012 11:16 AM, Wen Congyang Wrote:
> Hi, all
>
> 'virsh dump' can not work when host pci device is used by guest. We have
> discussed this issue here:
> http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html
>
> We have determined to introduce a new command dump to dump memory. The core
> file's format can be elf.
Hi, Jan Kiszka
At 01/10/2012 09:30 PM, Luiz Capitulino Wrote:
> Btw, I'd like to have an ack from Jan for the general approach of this
> command.
>
Do you agree with the general approach of this command?
Thanks
Wen Congyang
>
> Note:
> 1. The guest should be x86 or x86_64. The other arch is not supported.
> 2. If you use old gdb, gdb may crash. I use gdb-7.3.1, and it does not crash.
> 3. If the OS is in the second kernel, gdb may not work well, and crash can
> work by specifying '--machdep phys_addr=xxx' in the command line. The
> reason is that the second kernel will update the page table, and we can
> not get the page table for the first kernel.
> 4. If the guest OS is 32 bit and the memory size is larger than 4G, the vmcore
> is elf64 format. You should use the gdb which is built with --enable-64-bit-bfd.
> 5. This patchset is based on the upstream tree, and apply one patch that is still
> in Luiz Capitulino's tree, because I use the API qemu_get_fd() in this patchset.
>
> Changes from v5 to v6:
> 1. allow user to dump a fraction of the memory
> 2. fix some bugs
>
> Changes from v4 to v5:
> 1. convert the new command dump to QAPI
>
> Changes from v3 to v4:
> 1. support it to run asynchronously
> 2. add API to cancel dumping and query dumping progress
> 3. add API to control dumping speed
> 4. auto cancel dumping when the user resumes vm, and the status is failed.
>
> Changes from v2 to v3:
> 1. address Jan Kiszka's comment
>
> Changes from v1 to v2:
> 1. fix virt addr in the vmcore.
>
> Wen Congyang (16):
> monitor: introduce qemu_suspend_monitor()/qemu_resume_monitor()
> Add API to create memory mapping list
> Add API to check whether a physical address is I/O address
> target-i386: implement cpu_get_memory_mapping()
> Add API to get memory mapping
> target-i386: Add API to write elf notes to core file
> target-i386: Add API to add extra memory mapping
> target-i386: add API to get dump info
> introduce a new monitor command 'dump' to dump guest's memory
> run dump at the background
> support detached dump
> support to cancel the current dumping
> support to set dumping speed
> support to query dumping status
> auto cancel dumping after vm state is changed to run
> allow user to dump a fraction of the memory
>
> Makefile.target | 11 +-
> cpu-all.h | 18 +
> cpu-common.h | 2 +
> dump.c | 885 +++++++++++++++++++++++++++++++++++++++++++++++
> dump.h | 13 +
> exec.c | 16 +
> hmp-commands.hx | 49 +++
> hmp.c | 49 +++
> hmp.h | 4 +
> memory_mapping.c | 222 ++++++++++++
> memory_mapping.h | 41 +++
> monitor.c | 37 ++
> monitor.h | 2 +
> qapi-schema.json | 72 ++++
> qmp-commands.hx | 119 +++++++
> target-i386/arch-dump.c | 574 ++++++++++++++++++++++++++++++
> vl.c | 5 +-
> 17 files changed, 2112 insertions(+), 7 deletions(-)
> create mode 100644 dump.c
> create mode 100644 dump.h
> create mode 100644 memory_mapping.c
> create mode 100644 memory_mapping.h
> create mode 100644 target-i386/arch-dump.c
>
>
prev parent reply other threads:[~2012-02-13 1:42 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 3:16 [Qemu-devel] [RFC][PATCH 00/16 v6] introducing a new, dedicated memory dump mechanism Wen Congyang
2012-02-09 3:19 ` [Qemu-devel] [RFC][PATCH 01/16 v6] monitor: introduce qemu_suspend_monitor()/qemu_resume_monitor() Wen Congyang
2012-02-14 16:19 ` Jan Kiszka
2012-02-15 2:54 ` Wen Congyang
2012-02-15 8:51 ` Jan Kiszka
2012-02-15 13:01 ` Luiz Capitulino
2012-02-16 1:35 ` Wen Congyang
2012-02-09 3:20 ` [Qemu-devel] [RFC][PATCH 02/16 v6] Add API to create memory mapping list Wen Congyang
2012-02-14 16:39 ` Jan Kiszka
2012-02-15 3:00 ` Wen Congyang
2012-02-09 3:21 ` [Qemu-devel] [RFC][PATCH 03/16 v6] Add API to check whether a physical address is I/O address Wen Congyang
2012-02-14 16:52 ` Jan Kiszka
2012-02-15 3:03 ` Wen Congyang
2012-02-09 3:21 ` [Qemu-devel] [RFC][PATCH 04/16 v6] target-i386: implement cpu_get_memory_mapping() Wen Congyang
2012-02-14 17:07 ` Jan Kiszka
2012-02-15 3:05 ` Wen Congyang
2012-02-09 3:22 ` [Qemu-devel] [RFC][PATCH 05/16 v6] Add API to get memory mapping Wen Congyang
2012-02-14 17:21 ` Jan Kiszka
2012-02-15 4:07 ` Wen Congyang
2012-02-15 9:17 ` Jan Kiszka
2012-02-15 9:41 ` Wen Congyang
2012-02-15 9:47 ` HATAYAMA Daisuke
2012-02-15 10:19 ` Jan Kiszka
2012-02-09 3:24 ` [Qemu-devel] [RFC][PATCH 06/16 v6] target-i386: Add API to write elf notes to core file Wen Congyang
2012-02-14 17:31 ` Jan Kiszka
2012-02-15 3:16 ` Wen Congyang
2012-02-09 3:24 ` [Qemu-devel] [RFC][PATCH 07/16 v6] target-i386: Add API to add extra memory mapping Wen Congyang
2012-02-14 17:35 ` Jan Kiszka
2012-02-15 5:19 ` Wen Congyang
2012-02-15 9:21 ` Jan Kiszka
2012-02-15 9:44 ` Wen Congyang
2012-02-15 10:21 ` Jan Kiszka
2012-02-17 9:32 ` Wen Congyang
2012-02-17 11:34 ` HATAYAMA Daisuke
2012-02-09 3:26 ` [Qemu-devel] [RFC][PATCH 08/16 v6] target-i386: add API to get dump info Wen Congyang
2012-02-14 17:39 ` Jan Kiszka
2012-02-15 3:30 ` Wen Congyang
2012-02-15 9:05 ` Jan Kiszka
2012-02-15 9:10 ` Wen Congyang
2012-02-15 9:12 ` Peter Maydell
2012-02-15 9:19 ` Wen Congyang
2012-02-09 3:28 ` [Qemu-devel] [RFC][PATCH 09/16 v6] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2012-02-14 17:59 ` Jan Kiszka
2012-02-15 3:44 ` Wen Congyang
2012-02-17 8:52 ` Wen Congyang
2012-02-17 9:26 ` Jan Kiszka
2012-02-17 9:35 ` Wen Congyang
2012-02-17 9:35 ` Jan Kiszka
2012-02-17 16:32 ` Eric Blake
2012-02-17 16:51 ` Jan Kiszka
2012-02-17 17:05 ` Eric Blake
2012-02-09 3:28 ` [Qemu-devel] [RFC][PATCH 10/16 v6] run dump at the background Wen Congyang
2012-02-14 18:05 ` Jan Kiszka
2012-02-14 18:27 ` Jan Kiszka
2012-02-15 3:47 ` Wen Congyang
2012-02-15 9:07 ` Jan Kiszka
2012-02-15 9:22 ` Wen Congyang
2012-02-15 9:21 ` Jan Kiszka
2012-02-15 9:35 ` Wen Congyang
2012-02-15 10:16 ` Jan Kiszka
2012-02-09 3:29 ` [Qemu-devel] [RFC][PATCH 11/16 v6] support detached dump Wen Congyang
2012-02-09 3:30 ` [Qemu-devel] [RFC][PATCH 12/16 v6] support to cancel the current dumping Wen Congyang
2012-02-09 3:32 ` [Qemu-devel] [RFC][PATCH 13/16 v6] support to set dumping speed Wen Congyang
2012-02-09 3:32 ` [Qemu-devel] [RFC][PATCH 14/16 v6] support to query dumping status Wen Congyang
2012-02-09 3:33 ` [Qemu-devel] [RFC][PATCH 15/16 v6] auto cancel dumping after vm state is changed to run Wen Congyang
2012-02-09 3:34 ` [Qemu-devel] [RFC][PATCH 16/16 v6] allow user to dump a fraction of the memory Wen Congyang
2012-02-14 18:27 ` Jan Kiszka
2012-02-13 1:45 ` Wen Congyang [this message]
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=4F386B35.8050508@cn.fujitsu.com \
--to=wency@cn.fujitsu.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).