* [Qemu-devel] [PATCH] spice: set qxl->ssd.running=true before telling spice to start, RHBZ #733993
@ 2011-09-05 14:39 Yonit Halperin
2011-09-18 8:07 ` Alon Levy
0 siblings, 1 reply; 2+ messages in thread
From: Yonit Halperin @ 2011-09-05 14:39 UTC (permalink / raw)
To: qemu-devel; +Cc: Yonit Halperin, kraxel
If qxl->ssd.running=true is set after telling spice to start, the spice server
thread can call qxl_send_events while qxl->ssd.running is still false. This leads to
assert(d->ssd.running).
Signed-off-by: Yonit Halperin <yhalperi@redhat.com>
---
Since it looks like the purpose of the assert in qxl_send_event is preventing changes
in the guest when the vm is stopped, I think it is not necessary for ssd.running to be
exactly synchronized with the spice server status, but just be true before
the spice worker starts.
ui/spice-display.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/ui/spice-display.c b/ui/spice-display.c
index 683d454..3224f99 100644
--- a/ui/spice-display.c
+++ b/ui/spice-display.c
@@ -260,11 +260,12 @@ void qemu_spice_vm_change_state_handler(void *opaque, int running, int reason)
SimpleSpiceDisplay *ssd = opaque;
if (running) {
+ ssd->running = true;
qemu_spice_start(ssd);
} else {
qemu_spice_stop(ssd);
+ ssd->running = false;
}
- ssd->running = running;
}
void qemu_spice_display_init_common(SimpleSpiceDisplay *ssd, DisplayState *ds)
--
1.7.4.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] [PATCH] spice: set qxl->ssd.running=true before telling spice to start, RHBZ #733993
2011-09-05 14:39 [Qemu-devel] [PATCH] spice: set qxl->ssd.running=true before telling spice to start, RHBZ #733993 Yonit Halperin
@ 2011-09-18 8:07 ` Alon Levy
0 siblings, 0 replies; 2+ messages in thread
From: Alon Levy @ 2011-09-18 8:07 UTC (permalink / raw)
To: Yonit Halperin; +Cc: qemu-devel, kraxel
On Mon, Sep 05, 2011 at 05:39:50PM +0300, Yonit Halperin wrote:
> If qxl->ssd.running=true is set after telling spice to start, the spice server
> thread can call qxl_send_events while qxl->ssd.running is still false. This leads to
> assert(d->ssd.running).
>
Looks good.
Acked-by: Alon Levy <alevy@redhat.com>
> Signed-off-by: Yonit Halperin <yhalperi@redhat.com>
> ---
> Since it looks like the purpose of the assert in qxl_send_event is preventing changes
> in the guest when the vm is stopped, I think it is not necessary for ssd.running to be
> exactly synchronized with the spice server status, but just be true before
> the spice worker starts.
>
> ui/spice-display.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/ui/spice-display.c b/ui/spice-display.c
> index 683d454..3224f99 100644
> --- a/ui/spice-display.c
> +++ b/ui/spice-display.c
> @@ -260,11 +260,12 @@ void qemu_spice_vm_change_state_handler(void *opaque, int running, int reason)
> SimpleSpiceDisplay *ssd = opaque;
>
> if (running) {
> + ssd->running = true;
> qemu_spice_start(ssd);
> } else {
> qemu_spice_stop(ssd);
> + ssd->running = false;
> }
> - ssd->running = running;
> }
>
> void qemu_spice_display_init_common(SimpleSpiceDisplay *ssd, DisplayState *ds)
> --
> 1.7.4.4
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-09-18 8:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-05 14:39 [Qemu-devel] [PATCH] spice: set qxl->ssd.running=true before telling spice to start, RHBZ #733993 Yonit Halperin
2011-09-18 8:07 ` Alon Levy
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).