All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCT 0/14 v4] dump memory when host pci device is used by guest
Date: Tue, 10 Jan 2012 10:41:24 +0100	[thread overview]
Message-ID: <4F0C07C4.2080504@siemens.com> (raw)
In-Reply-To: <4F0BEC4F.9030904@cn.fujitsu.com>

On 2012-01-10 08:44, Wen Congyang wrote:
> Hi, Jan Kiszka
> Do you have any time to review this patchset?

Will try to find some.

BTW, the title of this cover letter is a bit misleading. This series is
about introducing a new, dedicated memory dump mechanism.

Jan

> 
> Thanks
> Wen Congyang
> 
> At 01/04/2012 01:44 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
>>
>> 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.
>>
>> Change 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.
>>
>> Change from v2 to v3:
>> 1. address Jan Kiszka's comment
>>
>> Changes from v1 to v2:
>> 1. fix virt addr in the vmcore.
>>
>> Wen Congyang (14):
>>   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
>>
>>  Makefile.target         |   11 +-
>>  cpu-all.h               |   18 +
>>  cpu-common.h            |    2 +
>>  dump.c                  |  796 +++++++++++++++++++++++++++++++++++++++++++++++
>>  dump.h                  |   14 +
>>  exec.c                  |   20 ++
>>  hmp-commands.hx         |   47 +++
>>  hmp.c                   |   24 ++
>>  hmp.h                   |    3 +
>>  memory_mapping.c        |  185 +++++++++++
>>  memory_mapping.h        |   39 +++
>>  monitor.c               |   10 +
>>  qapi-schema.json        |   54 ++++
>>  qmp-commands.hx         |  117 +++++++
>>  target-i386/arch-dump.c |  574 ++++++++++++++++++++++++++++++++++
>>  15 files changed, 1909 insertions(+), 5 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
>>
>>
> 

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      reply	other threads:[~2012-01-10  9:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  5:44 [Qemu-devel] [RFC][PATCT 0/14 v4] dump memory when host pci device is used by guest Wen Congyang
2012-01-04  6:04 ` [Qemu-devel] [RFC][PATCH 01/14 v4] Add API to create memory mapping list Wen Congyang
2012-01-04  6:05 ` [Qemu-devel] [RFC][PATCH 02/14 v4] Add API to check whether a physical address is I/O address Wen Congyang
2012-01-04  6:06 ` [Qemu-devel] [RFC][PATCH 03/14 v4] target-i386: implement cpu_get_memory_mapping() Wen Congyang
2012-01-04  6:07 ` [Qemu-devel] [RFC][PATCH 04/14 v4] Add API to get memory mapping Wen Congyang
2012-01-04  6:08 ` [Qemu-devel] [RFC][PATCH 05/14 v4] target-i386: Add API to write elf notes to core file Wen Congyang
2012-01-04  6:09 ` [Qemu-devel] [RFC][PATCH 06/14 v4] target-i386: Add API to add extra memory mapping Wen Congyang
2012-01-04  6:10 ` [Qemu-devel] [RFC][PATCH 07/14 v4] target-i386: add API to get dump info Wen Congyang
2012-01-04  6:11 ` [Qemu-devel] [RFC][PATCH 08/14 v4] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2012-01-10 13:30   ` Luiz Capitulino
2012-01-11  0:59     ` Wen Congyang
2012-01-12 13:49       ` Luiz Capitulino
2012-01-13  8:35         ` Wen Congyang
2012-01-04  6:12 ` [Qemu-devel] [RFC][PATCH 09/14 v4] run dump at the background Wen Congyang
2012-01-04  6:13 ` [Qemu-devel] [RFC][PATCH 10/14 v4] support detached dump Wen Congyang
2012-01-04  6:14 ` [Qemu-devel] [RFC][PATCH 11/14 v4] support to cancel the current dumping Wen Congyang
2012-01-04  6:15 ` [Qemu-devel] [RFC][PATCH 12/14 v4] support to set dumping speed Wen Congyang
2012-01-04  6:16 ` [Qemu-devel] [RFC][PATCH 13/14 v4] support to query dumping status Wen Congyang
2012-01-04  6:17 ` [Qemu-devel] [RFC][PATCH 14/14 v4] auto cancel dumping after vm state is changed to run Wen Congyang
2012-01-10  7:44 ` [Qemu-devel] [RFC][PATCT 0/14 v4] dump memory when host pci device is used by guest Wen Congyang
2012-01-10  9:41   ` Jan Kiszka [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=4F0C07C4.2080504@siemens.com \
    --to=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 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.