From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Dave Anderson <anderson@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 00/12 v11] introducing a new, dedicated guest memory dump mechanism
Date: Tue, 03 Apr 2012 09:35:24 +0200 [thread overview]
Message-ID: <4F7AA83C.7050005@siemens.com> (raw)
In-Reply-To: <4F791ABA.5030507@cn.fujitsu.com>
On 2012-04-02 05:19, Wen Congyang wrote:
> At 03/28/2012 08:44 PM, Luiz Capitulino Wrote:
>> On Wed, 28 Mar 2012 13:17:43 +0800
>> Wen Congyang <wency@cn.fujitsu.com> wrote:
>>
>>> Hi, Luiz, Anthony, Jan
>>>
>>> do you have any comments about this patchset?
>>
>> As far as QMP is concerned:
>>
>> Acked-by: Luiz Capitulino <lcapitulino@redhat.com>
>
> I fix a overflow bug and resend patch 12/12
>
>>
>> This can go through me tree, but I'd like an ACK from Jan and/or Anthony.
>>
>
> Hi, Jan, Anthony
>
> when do you have tiem to review this patchset?
High on my to-do list. I hope to have a look and a try the next days.
Sorry for the long delay.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-04-03 7:35 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
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 [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=4F7AA83C.7050005@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=anderson@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=eblake@redhat.com \
--cc=lcapitulino@redhat.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 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).