From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42764)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <qiaonuohan@cn.fujitsu.com>) id 1UlreK-000707-1V
	for qemu-devel@nongnu.org; Sun, 09 Jun 2013 22:16:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <qiaonuohan@cn.fujitsu.com>) id 1UlreH-0004DE-K2
	for qemu-devel@nongnu.org; Sun, 09 Jun 2013 22:15:59 -0400
Received: from [222.73.24.84] (port=31796 helo=song.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <qiaonuohan@cn.fujitsu.com>) id 1UlreH-0004Ae-8o
	for qemu-devel@nongnu.org; Sun, 09 Jun 2013 22:15:57 -0400
Message-ID: <51B536C7.5050300@cn.fujitsu.com>
Date: Mon, 10 Jun 2013 10:15:35 +0800
From: Qiao Nuohan <qiaonuohan@cn.fujitsu.com>
MIME-Version: 1.0
References: <1369709437-24969-1-git-send-email-qiaonuohan@cn.fujitsu.com>
	<51AE946F.8040108@cn.fujitsu.com>
	<20130604221541.75bef4dd@redhat.com>
In-Reply-To: <20130604221541.75bef4dd@redhat.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Subject: Re: [Qemu-devel] [PATCH v4 0/9] Make 'dump-guest-memory' dump in
 kdump-compressed format
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Amos <akong@redhat.com>, qemu-devel@nongnu.org, armbru@redhat.com, zhangxh@cn.fujitsu.com, anderson@redhat.com, kumagai-atsushi@mxc.nes.nec.co.jp, afaerber@suse.de

On 06/05/2013 10:15 AM, Luiz Capitulino wrote:
> I can review it until the end of this week. If this series is adding a new
> argument (which I believe is what it does) then there's only two ways
> to get this merged: either we wait for full introspection or you add this
> feature as a new command.
>
> I'd prefer to wait for full introspection, but it depends how long it's
> going to take to get it merged and how much time you're willing to wait.
>
> Amos, can you give us an update on that work?

Hi Luiz,

I would like to get these patches reviewed first. If introspection won't take
too much time, I will choose to wait. However, I cannot figure out how long it
will take, why not get the parts not related to introspection settled first?

Seems Amos's draft will not change qapi-schema.json.

-- 
Regards
Qiao Nuohan