From: Wen Congyang <wency@cn.fujitsu.com>
To: Luiz Capitulino <lcapitulino@redhat.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>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [RFC][PATCH 00/16 v8] introducing a new, dedicated memory dump mechanism
Date: Thu, 08 Mar 2012 16:55:37 +0800 [thread overview]
Message-ID: <4F587409.3020101@cn.fujitsu.com> (raw)
In-Reply-To: <20120307143854.01cfeef2@doriath.home>
At 03/08/2012 01:38 AM, Luiz Capitulino Wrote:
> On Mon, 5 Mar 2012 21:41:02 -0300
> Luiz Capitulino <lcapitulino@redhat.com> wrote:
>
>> On Mon, 05 Mar 2012 17:12:00 +0800
>> Wen Congyang <wency@cn.fujitsu.com> wrote:
>>
>>> At 03/02/2012 05:59 PM, 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
>>>>
>>>> The last version is here:
>>>> http://lists.nongnu.org/archive/html/qemu-devel/2012-02/msg04228.html
>>>>
>>>> We have determined to introduce a new command dump to dump memory. The core
>>>> file's format can be elf.
>>>>
>>>> Note:
>>>> 1. The guest should be x86 or x86_64. The other arch is not supported now.
>>>> 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. The cpu's state is stored in QEMU note. You neet to modify crash to use
>>>> it to calculate phys_base.
>>>> 5. 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.
>>>> 6. 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.
>>>>
>>>
>>> Hi, Jan, Luiz Capitulino
>>> Do you have any comments?
>>
>> I haven't had a chance to review it yet, will do in the next few days.
>
> Wen, I've started reviewing this but before I ask you to make more changes
> to this series, it's better to wait for a conclusion of the asynchronous
> command discussion thread:
>
> http://lists.gnu.org/archive/html/qemu-devel/2012-03/msg01067.html
OK. I see this thread.
Thanks
Wen Congyang
>
>
>
prev parent reply other threads:[~2012-03-08 8:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 9:59 [Qemu-devel] [RFC][PATCH 00/16 v8] introducing a new, dedicated memory dump mechanism Wen Congyang
2012-03-02 10:02 ` [Qemu-devel] [RFC][PATCH 01/16 v8] Add API to create memory mapping list Wen Congyang
2012-03-02 10:06 ` [Qemu-devel] [RFC][PATCH 02/16 v8] Add API to check whether a physical address is I/O address Wen Congyang
2012-03-02 10:08 ` [Qemu-devel] [RFC][PATCH 03/16 v8] implement cpu_get_memory_mapping() Wen Congyang
2012-03-02 10:12 ` [Qemu-devel] [RFC][PATCH 04/16 v8] Add API to check whether paging mode is enabled Wen Congyang
2012-03-02 10:18 ` [Qemu-devel] [RFC][PATCH 05/16 v8] Add API to get memory mapping Wen Congyang
2012-03-07 15:27 ` HATAYAMA Daisuke
2012-03-08 8:52 ` Wen Congyang
2012-03-09 0:40 ` HATAYAMA Daisuke
2012-03-09 1:46 ` Wen Congyang
2012-03-09 2:05 ` HATAYAMA Daisuke
2012-03-09 2:26 ` Wen Congyang
2012-03-09 2:53 ` HATAYAMA Daisuke
2012-03-09 9:41 ` Jan Kiszka
2012-03-09 9:57 ` Wen Congyang
2012-03-09 10:05 ` Jan Kiszka
2012-03-09 10:06 ` Jan Kiszka
2012-03-09 12:53 ` HATAYAMA Daisuke
2012-03-09 13:24 ` Jan Kiszka
2012-03-12 6:16 ` HATAYAMA Daisuke
2012-03-12 6:26 ` HATAYAMA Daisuke
2012-03-12 1:52 ` Wen Congyang
2012-03-09 9:43 ` Jan Kiszka
2012-03-02 10:23 ` [Qemu-devel] [RFC][PATCH 06/16 v8] Add API to get memory mapping without doing paging Wen Congyang
2012-03-02 10:27 ` [Qemu-devel] [RFC][PATCH 07/16 v8] target-i386: Add API to write elf notes to core file Wen Congyang
2012-03-02 10:31 ` [Qemu-devel] [RFC][PATCH 08/16 v8] target-i386: Add API to write cpu status " Wen Congyang
2012-03-02 10:33 ` [Qemu-devel] [RFC][PATCH 09/16 v8] target-i386: add API to get dump info Wen Congyang
2012-03-02 10:38 ` [Qemu-devel] [RFC][PATCH 10/16 v8] make gdb_id() generally avialable Wen Congyang
2012-03-02 10:42 ` [Qemu-devel] [RFC][PATCH 11/16 v8] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2012-03-02 10:43 ` [Qemu-devel] [RFC][PATCH 12/16 v8] support to cancel the current dumping Wen Congyang
2012-03-02 10:44 ` [Qemu-devel] [RFC][PATCH 13/16 v8] support to query dumping status Wen Congyang
2012-03-02 10:44 ` [Qemu-devel] [RFC][PATCH 14/16 v8] run dump at the background Wen Congyang
2012-03-02 10:45 ` [Qemu-devel] [RFC][PATCH 15/16 v8] support detached dump Wen Congyang
2012-03-02 10:46 ` [Qemu-devel] [RFC][PATCH 16/16 v8] allow user to dump a fraction of the memory Wen Congyang
2012-03-05 9:12 ` [Qemu-devel] [RFC][PATCH 00/16 v8] introducing a new, dedicated memory dump mechanism Wen Congyang
2012-03-06 0:41 ` Luiz Capitulino
2012-03-07 17:38 ` Luiz Capitulino
2012-03-08 8:55 ` 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=4F587409.3020101@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.