From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Um1cR-0007SA-Ok for qemu-devel@nongnu.org; Mon, 10 Jun 2013 08:54:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Um1cM-0003mU-OM for qemu-devel@nongnu.org; Mon, 10 Jun 2013 08:54:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57159) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Um1cM-0003mJ-G7 for qemu-devel@nongnu.org; Mon, 10 Jun 2013 08:54:38 -0400 Date: Mon, 10 Jun 2013 08:54:25 -0400 From: Luiz Capitulino Message-ID: <20130610085425.1a9bef34@redhat.com> In-Reply-To: <51B536C7.5050300@cn.fujitsu.com> References: <1369709437-24969-1-git-send-email-qiaonuohan@cn.fujitsu.com> <51AE946F.8040108@cn.fujitsu.com> <20130604221541.75bef4dd@redhat.com> <51B536C7.5050300@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 0/9] Make 'dump-guest-memory' dump in kdump-compressed format List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Qiao Nuohan Cc: Amos , 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 Mon, 10 Jun 2013 10:15:35 +0800 Qiao Nuohan wrote: > 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? What do you mean by "settled"? We can keep the review cycle going, but to merge this we have two options: we wait for the full introspection or we make this a different command. > Seems Amos's draft will not change qapi-schema.json. The point of Amos series is discovery, not conflicts. If we merge your series w/o introspection support, then it's impossible for a mngt app like libvirt to know whether or not a given QEMU version supports your new argument.