qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	Dave Anderson <anderson@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCT 0/5 v2] dump memory when host pci device is used by guest
Date: Wed, 14 Dec 2011 10:43:36 +0800	[thread overview]
Message-ID: <4EE80D58.1040805@cn.fujitsu.com> (raw)
In-Reply-To: <4EE74B28.9040502@siemens.com>

At 12/13/2011 08:55 PM, Jan Kiszka Write:
> On 2011-12-09 08:57, 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.
>>
>> 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.
>>
>> Changes from v1 to v2:
>> 1. fix virt addr in the vmcore.
>>
>> Wen Congyang (5):
>>   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
>>   introduce a new monitor command 'dump' to dump guest's memory
>>
>>  Makefile.target      |    9 +-
>>  cpu-all.h            |   10 +
>>  cpu-common.h         |    1 +
>>  dump.c               |  722 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>  dump.h               |    6 +
>>  exec.c               |   20 ++
>>  hmp-commands.hx      |   16 ++
>>  memory_mapping.c     |  183 +++++++++++++
>>  memory_mapping.h     |   30 ++
>>  monitor.c            |    3 +
>>  qmp-commands.hx      |   24 ++
>>  target-i386/helper.c |  239 +++++++++++++++++
>>  12 files changed, 1259 insertions(+), 4 deletions(-)
>>  create mode 100644 dump.c
>>  create mode 100644 dump.h
>>  create mode 100644 memory_mapping.c
>>  create mode 100644 memory_mapping.h
> 
> A general remark regarding code organization: Please factor out the
> target specific bits and push them into target-*/dump.[ch] or whatever
> appropriate file in that folder. Ugly #ifdefs should be avoided in
> generic code as far as possible.

OK. I will fix it. Thanks for pointing it out.

Thanks
Wen Congyang

> 
> Thanks,
> Jan
> 

      reply	other threads:[~2011-12-14  2:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09  7:57 [Qemu-devel] [RFC][PATCT 0/5 v2] dump memory when host pci device is used by guest Wen Congyang
2011-12-09  8:06 ` [Qemu-devel] [RFC][PATCH 1/5 v2] Add API to create memory mapping list Wen Congyang
2011-12-13 13:03   ` Jan Kiszka
2011-12-14  8:10     ` Wen Congyang
2011-12-09  8:07 ` [Qemu-devel] [RFC][PATCH 2/5 v2] Add API to check whether a physical address is I/O address Wen Congyang
2011-12-09  8:08 ` [Qemu-devel] [RFC][PATCH 3/5 v2] target-i386: implement cpu_get_memory_mapping() Wen Congyang
2011-12-09  8:09 ` [Qemu-devel] [RFC][PATCH 4/5 v2] Add API to get memory mapping Wen Congyang
2011-12-09  8:09 ` [Qemu-devel] [RFC][PATCH 5/5v2] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2011-12-13  3:12 ` [Qemu-devel] [RFC][PATCT 0/5 v2] dump memory when host pci device is used by guest HATAYAMA Daisuke
2011-12-13  3:35   ` Wen Congyang
2011-12-13  6:01     ` HATAYAMA Daisuke
2011-12-13  9:20       ` Wen Congyang
2011-12-15  1:30         ` HATAYAMA Daisuke
2011-12-15  8:57           ` Wen Congyang
2011-12-13 12:55 ` Jan Kiszka
2011-12-14  2:43   ` 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=4EE80D58.1040805@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=anderson@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=jan.kiszka@siemens.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).