Re: [Qemu-devel] [PATCH v5 0/9] Make 'dump-guest-memory' dump in kdump-compressed format

[Eric Blake <eblake@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]

On 12/12/2013 07:07 PM, Qiao Nuohan wrote:
> Hi, all
> 
> Would you please give some advice about how to continue my series?
> 
> 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 completion
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).

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]