From: Amit Shah <amit.shah@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] spice-qemu-char: register interface on post load
Date: Mon, 24 Dec 2012 13:09:20 +0530 [thread overview]
Message-ID: <20121224073920.GC21637@amit.redhat.com> (raw)
In-Reply-To: <1356298529-7334-1-git-send-email-alevy@redhat.com>
On (Sun) 23 Dec 2012 [23:35:29], Alon Levy wrote:
> 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 | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
I suppose Gerd should pick this up in his tree?
I have a couple of questions below, but I ack this approach.
> static QLIST_HEAD(, SpiceCharDriver) spice_chars =
> @@ -185,18 +190,23 @@ static void spice_chr_close(struct CharDriverState *chr)
> printf("%s\n", __func__);
> vmc_unregister_interface(s);
> QLIST_REMOVE(s, next);
> + qemu_free_timer(s->post_load.timer);
Also vmstate_unregister()?
I'm wondering if there can be a case where this function is called
before the timer has had a chance to fire. It can happen if the spice
port is hot-unplugged before the guest has had a chance to run on the
target. In that case, qemu_del_timer() should be called as well, to
ensure the timer doesn't fire with invalid args later.
Amit
next prev parent reply other threads:[~2012-12-24 7:39 UTC|newest]
Thread overview: 23+ 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
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 [this message]
[not found] <20130227123728.GA10426@amit.redhat.com>
2013-03-14 15:12 ` Alon Levy
2013-03-14 16:39 ` Hans de Goede
2013-03-14 16:40 ` Alon Levy
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=20121224073920.GC21637@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=alevy@redhat.com \
--cc=anthony@codemonkey.ws \
--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).