qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: amit shah <amit.shah@redhat.com>,
	qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCH 3/3] spice-qemu-char: register interface on	post load
Date: Wed, 28 Nov 2012 04:51:55 -0500 (EST)	[thread overview]
Message-ID: <944749120.38926128.1354096315182.JavaMail.root@redhat.com> (raw)
In-Reply-To: <87sj7uvz3i.fsf@blackfin.pond.sub.org>

> Alon Levy <alevy@redhat.com> writes:
> 
> > The target has not seen the guest_connected event via
> > spice_chr_guest_open or spice_chr_write, and so spice server
> > wrongly
> > assumes there is no agent active, while the client continues to
> > send
> > motion events only by the agent channel, which the server ignores.
> > The
> > net effect is that the mouse is static in the guest.
> >
> > By registering the interface on post load spice server will pass on
> > the
> > agent messages fixing the mouse behavior after migration.
> >
> > RHBZ #725965
> >
> > Signed-off-by: Alon Levy <alevy@redhat.com>
> > ---
> >  spice-qemu-char.c | 34 ++++++++++++++++++++++++++++++++++
> >  1 file changed, 34 insertions(+)
> >
> > diff --git a/spice-qemu-char.c b/spice-qemu-char.c
> > index 09aa22d..08b6ba0 100644
> > --- a/spice-qemu-char.c
> > +++ b/spice-qemu-char.c
> > @@ -1,6 +1,7 @@
> >  #include "config-host.h"
> >  #include "trace.h"
> >  #include "ui/qemu-spice.h"
> > +#include "hw/virtio-serial.h"
> >  #include <spice.h>
> >  #include <spice-experimental.h>
> >  
> > @@ -25,6 +26,7 @@ typedef struct SpiceCharDriver {
> >      uint8_t               *datapos;
> >      ssize_t               bufsize, datalen;
> >      uint32_t              debug;
> > +    QEMUTimer             *post_load_timer;
> >  } SpiceCharDriver;
> >  
> >  static int vmc_write(SpiceCharDeviceInstance *sin, const uint8_t
> >  *buf, int len)
> > @@ -156,6 +158,7 @@ static void spice_chr_close(struct
> > CharDriverState *chr)
> >  
> >      printf("%s\n", __func__);
> >      vmc_unregister_interface(s);
> > +    qemu_free_timer(s->post_load_timer);
> >      g_free(s);
> >  }
> >  
> > @@ -188,6 +191,33 @@ static void print_allowed_subtypes(void)
> >      fprintf(stderr, "\n");
> >  }
> >  
> > +static void spice_chr_post_load_cb(void *opaque)
> > +{
> > +    SpiceCharDriver *s = opaque;
> > +
> > +    vmc_register_interface(s);
> > +}
> > +
> > +static int spice_chr_post_load(void *opaque, int version_id)
> > +{
> > +    SpiceCharDriver *s = opaque;
> > +
> > +    if (s && s->chr && qemu_chr_be_connected(s->chr)) {
> > +        qemu_mod_timer(s->post_load_timer, 1);
> > +    }
> 
> You use the time to delay spice_chr_post_load_cb(), right?  Can you
> explain why you have to delay?

This is a precaution, it ensures vmc_register_interface is called when the vm is running as opposed to stopped which is the state when spice_chr_post_load is called. In theory vmc_register_interface could lead to an attempt to inject an interrupt into the guest, and we know that fails with kvm irqchip from a previous bug with virtio-serial.

> 
> > +    return 0;
> > +}
> > +
> > +static VMStateDescription spice_chr_vmstate = {
> > +    .name               = "spice-chr",
> > +    .version_id         = 1,
> > +    .minimum_version_id = 1,
> > +    .post_load          = spice_chr_post_load,
> > +    .fields = (VMStateField[]) {
> > +        VMSTATE_END_OF_LIST()
> > +    },
> > +};
> > +
> >  CharDriverState *qemu_chr_open_spice(QemuOpts *opts)
> >  {
> >      CharDriverState *chr;
> > @@ -220,12 +250,16 @@ CharDriverState *qemu_chr_open_spice(QemuOpts
> > *opts)
> >      s->debug = debug;
> >      s->active = false;
> >      s->sin.subtype = subtype;
> > +    s->post_load_timer = qemu_new_timer_ns(vm_clock,
> > +                                           spice_chr_post_load_cb,
> > s);
> >      chr->opaque = s;
> >      chr->chr_write = spice_chr_write;
> >      chr->chr_close = spice_chr_close;
> >      chr->chr_guest_open = spice_chr_guest_open;
> >      chr->chr_guest_close = spice_chr_guest_close;
> >  
> > +    vmstate_register(NULL, -1, &spice_chr_vmstate, s);
> > +
> >  #if SPICE_SERVER_VERSION < 0x000901
> >      /* See comment in vmc_state() */
> >      if (strcmp(subtype, "vdagent") == 0) {
> 
> 

  reply	other threads:[~2012-11-28  9:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 13:39 [Qemu-devel] [PATCH] hw/virtio-serial-bus: replay guest open on destination Alon Levy
2012-11-27 12:48 ` Amit Shah
2012-11-27 14:10   ` Markus Armbruster
2012-11-27 14:34     ` Amit Shah
2012-11-27 19:03   ` Anthony Liguori
2012-11-28  9:05     ` [Qemu-devel] [PATCH 0/3] chardev/spice: fix missing spice mouse after migration Alon Levy
2012-11-28  9:05       ` [Qemu-devel] [PATCH 1/3] virtio-serial: add virtio_serial_guest_connected Alon Levy
2012-11-28  9:05       ` [Qemu-devel] [PATCH 2/3] qemu-char: add qemu_chr_be_connected Alon Levy
2012-11-28  9:42         ` Markus Armbruster
2012-11-28  9:05       ` [Qemu-devel] [PATCH 3/3] spice-qemu-char: register interface on post load Alon Levy
2012-11-28  9:46         ` Markus Armbruster
2012-11-28  9:51           ` Alon Levy [this message]
2012-11-28 11:59             ` Markus Armbruster
2012-11-28 12:16               ` Alon Levy
2012-11-29 13:08               ` Amit Shah
2012-12-13 10:54       ` [Qemu-devel] [PATCH 0/3] chardev/spice: fix missing spice mouse after migration Amit Shah
2012-12-13 14:25         ` Anthony Liguori
2012-12-14  4:10           ` Amit Shah
2012-12-23 21:35             ` [Qemu-devel] [PATCH] spice-qemu-char: register interface on post load Alon Levy
2012-12-24  7:39               ` Amit Shah

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=944749120.38926128.1354096315182.JavaMail.root@redhat.com \
    --to=alevy@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@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).