From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrIRz-0006Yl-PH for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:26:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrIRu-0004Kj-Sh for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:25:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42612) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrIRu-0004Kf-KE for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:25:54 -0500 Message-ID: <52AA7028.2090008@redhat.com> Date: Thu, 12 Dec 2013 19:25:44 -0700 From: Eric Blake MIME-Version: 1.0 References: <1373355014-14846-1-git-send-email-qiaonuohan@cn.fujitsu.com> <52AA6BD0.5060302@cn.fujitsu.com> In-Reply-To: <52AA6BD0.5060302@cn.fujitsu.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BDGVIbDwPSK7S6IgB33h4a0s2Hguw537b" Subject: Re: [Qemu-devel] [PATCH v5 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 , lcapitulino@redhat.com, zhangxh@cn.fujitsu.com, Amos Cc: stefanha@gmail.com, kumagai-atsushi@mxc.nes.nec.co.jp, anderson@redhat.com, afaerber@suse.de, qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BDGVIbDwPSK7S6IgB33h4a0s2Hguw537b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/12/2013 07:07 PM, Qiao Nuohan wrote: > Hi, all >=20 > Would you please give some advice about how to continue my series? >=20 > My patches have stuck for several months, because I was not allowed to > add an > option before introspection is implemented. After observing mails about= > introspection, I find it is still not confirmed its implement way. I can see several options: 1. Take over the introspection patches and push them through to completio= n 2. Come up with some alternative witness when your feature is available. Full-blown introspection of the entire QAPI schema is a heavy hammer, and if we can have something simpler to use for just this case, but still discoverable, then management can use that simpler method to learn if this feature is present. See for example how we added 'query-migrate-capabilities' as a way to add migration capabilities without needing fullblown introspection. 3. Rebase your patches and post without waiting for any means of discovery - maybe someone will still be interested enough in using the patches even without management being able to programmatically determine the availability. This is a busy list; it doesn't mean your patch will be outright rejected, but if you aren't actively pinging and rebasing it, the patch gets less attention, so people assume no one wanted it. Thanks for reviving the discussion, and good luck with what you try next. Personally, I think that both option 1 and 2 at the same time is worth pursuing (I'd really like introspection, but introspection is a heavy hammer so having something lighter weight for just your feature is also worth having). --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --BDGVIbDwPSK7S6IgB33h4a0s2Hguw537b Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJSqnAoAAoJEKeha0olJ0NqXtAH+wQxq2O7lqEsD9ns+ML3+Evt gmo0cd4Sul6EO/WqAXP6gksMkrmHGJ9dUazC28j1MueXd+RHx+VoSNK79LCQmYw+ dvFzMpG5bg2TVd7aw5mXT0S8LdBtmTfv+AGfQd/7/z4Rts/CFpq9V15EsR0olNnh ag6Ej6/MOLmeBbnW2/np8KC7Iz5hk+sJgg7JXDtVHIMz30CJvaKR/ypEspMGzyHE cHBgqzlvAFTUSJfG/otwnKj5joHVp0aD0CcOEgATMf1GklexQDKtNhYf6WH/azN3 4NXOzJn9PDHEuBgv/ln5fAxWFVMaK4lT/8HqRvaLn/p8VgtbaAe7tghQb6MvQS4= =UCjw -----END PGP SIGNATURE----- --BDGVIbDwPSK7S6IgB33h4a0s2Hguw537b--