From: Javier Celaya <javier.celaya@flexvm.es>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, devel@flexvm.es,
Gerd Hoffmann <kraxel@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
spice-devel <spice-devel@lists.freedesktop.org>
Subject: Re: [Qemu-devel] [Spice-devel] [PATCH] [RFC] LZ4 compression option for SPICE
Date: Wed, 28 Jan 2015 17:54:45 +0100 [thread overview]
Message-ID: <1497737.FQv3Yx42uv@javinlg> (raw)
In-Reply-To: <87r3ug8w9o.fsf@blackfin.pond.sub.org>
>From what I've seen in QEMU and libvirt's code, I would say that discovering
whether the spice server supports LZ4 is not a matter of adding a new QMP
command. That would not scale very well with new command line options. I would
suggest something more general. For instance, having the command query-
command-line-options return also the allowed values for string parameters.
That would output "lz4" for parameter "image-compression" in option "spice",
among the other compression methods. Another possibility would be a new QMP
command that returns the capabilities of the spice server, as defined in the
spice protocol. They include the SPICE_DISPLAY_CAP_LZ4_COMPRESSION capability,
if the spice server supports LZ4. In any case, I think it is out of the scope
of this patch.
El Martes, 27 de enero de 2015 09:26:11 Markus Armbruster escribió:
> Eric Blake <eblake@redhat.com> writes:
> > On 01/26/2015 01:48 AM, Javier Celaya wrote:
> >> Sorry, I forgot to patch the command-line help. Hope it helps.
> >>
> >>>> Recently, SPICE included the lz4 compression algorithm. This patch adds
> >>>> a command line option to select it.
> >>>
> >>> How is libvirt going to introspect whether the command line supports
> >>> this option? Is there some QMP command that lists the set of valid
> >>> compression formats understood by a given qemu binary?
> >
> > No, patching the command line --help does NOT help libvirt. It needs to
> > be discoverable via QMP to be introspectible, as scraping --help output
> > is not machine-friendly. (That said, you DO want to expose it in --help
> > output; I'm just complaining that --help output alone is not enough).
>
> We should really, really, really provide access to (the relevant subset
> of) the QAPI schema over QMP! Until we get that, useful progress is
> delayed by problems like this one, and we keep growing special-purpose
> solutions to problems like this one.
next prev parent reply other threads:[~2015-01-28 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 10:50 [Qemu-devel] [PATCH] [RFC] LZ4 compression option for SPICE Javier Celaya
2015-01-08 11:28 ` Gerd Hoffmann
2015-01-08 11:48 ` [Qemu-devel] [Spice-devel] " Fabio Fantoni
2015-01-08 12:00 ` Javier Celaya
2015-01-20 16:08 ` Christophe Fergeau
2015-01-23 14:06 ` Javier Celaya
2015-01-23 16:25 ` Eric Blake
2015-01-26 8:48 ` Javier Celaya
2015-01-26 16:25 ` Eric Blake
2015-01-27 8:26 ` Markus Armbruster
2015-01-28 16:54 ` Javier Celaya [this message]
2015-01-28 19:08 ` Markus Armbruster
2015-07-24 14:12 ` Fabio Fantoni
2015-07-27 6:12 ` Markus Armbruster
2015-10-09 6:45 ` Fabio Fantoni
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=1497737.FQv3Yx42uv@javinlg \
--to=javier.celaya@flexvm.es \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=devel@flexvm.es \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
/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).