From: Luiz Capitulino <lcapitulino@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add SPICE support to add_client monitor command
Date: Fri, 10 Feb 2012 15:40:10 -0200 [thread overview]
Message-ID: <20120210154010.3bc184dd@doriath.home> (raw)
In-Reply-To: <4F34FFCD.8040603@redhat.com>
On Fri, 10 Feb 2012 12:30:21 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:
> On 02/07/12 15:38, Daniel P. Berrange wrote:
> > From: "Daniel P. Berrange" <berrange@redhat.com>
> >
> > This is a followup to
> >
> > http://patchwork.ozlabs.org/patch/121004/
> >
> > With the acceptance of some new APIs to libspice-server.so it
> > is possible to add support for SPICE to the 'add_client'
> > monitor command, bringing parity with VNC. Since SPICE can
> > use TLS or plain connections, the command also gains a new
> > 'tls' parameter to specify whether TLS should be attempted
> > on the injected client sockets.
> >
> > This new feature is only enabled if building against a
> > libspice-server >= 0.10.1
> >
> > * qmp-commands.hx: Add 'tls' parameter & missing doc for
> > 'skipauth' parameter
> > * monitor.c: Wire up SPICE for 'add_client' command
> > * ui/qemu-spice.h, ui/spice-core.c: Add qemu_spice_display_add_client
> > API to wire up from monitor
>
> Spice bits are sane, the monitor bits look good to me too.
>
> Luiz? Can you have a look at the monitor bits? If you ack I'll go
> queue it up for the next spice update. Or you can just grab it and
> merge via qmp tree.
Reviewed. Will need a respin. Will ack v3 and you merge it through the
spice queue.
next prev parent reply other threads:[~2012-02-10 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 14:38 [Qemu-devel] [PATCH v2] Add SPICE support to add_client monitor command Daniel P. Berrange
2012-02-10 11:30 ` Gerd Hoffmann
2012-02-10 17:40 ` Luiz Capitulino [this message]
2012-02-10 17:38 ` Luiz Capitulino
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=20120210154010.3bc184dd@doriath.home \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).