Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread Jeremy White 

On 09/08/2014 03:33 PM, nicolas prochazka wrote:

sorry,
nothing , a lot of video frames seems to be drop.


The issue that my patch would solve, if you had encountered this 
problem, would be random crashes and hangs.  There was some sense that 
you lost sound after a few minutes.  Is that problem changed by this patch?


Cheers,

Jeremy
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread nicolas prochazka 
sorry,
nothing , a lot of video frames seems to be drop.

2014-09-08 20:39 GMT+02:00 Jeremy White :

> Hi Nicolas,
>
> On 09/08/2014 12:56 PM, nicolas prochazka wrote:
>
>> Hello,
>> I've done  differents tests, with the differents combinaisons between
>> qemu X and spice-server,
>> I can say  that is  since video adaptative streaming, the video
>> streaming is bad compare to the  old version (spice 0.12.3 / qemu 1.7 ).
>> When i set SPICE_DISABLE_ADAPTIVE_STREAMING=Y , my tests shows that's a
>> lot of frames are dropping, because of sound synchronisation, The only
>> way to get good streaming performance is to desactivate audio from
>> client side. ( --spice-disable-audio).
>>
>> An other point, when you disable streaming detection from server side,
>> video is good, but the sound is very bad.
>>
>
> I would be curious if my patch changes anything for you:
>
> http://lists.freedesktop.org/archives/spice-devel/2014-
> September/017334.html
>
> Cheers,
>
> Jeremy
>
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread Jeremy White 

Hi Nicolas,

On 09/08/2014 12:56 PM, nicolas prochazka wrote:

Hello,
I've done  differents tests, with the differents combinaisons between
qemu X and spice-server,
I can say  that is  since video adaptative streaming, the video
streaming is bad compare to the  old version (spice 0.12.3 / qemu 1.7 ).
When i set SPICE_DISABLE_ADAPTIVE_STREAMING=Y , my tests shows that's a
lot of frames are dropping, because of sound synchronisation, The only
way to get good streaming performance is to desactivate audio from
client side. ( --spice-disable-audio).

An other point, when you disable streaming detection from server side,
video is good, but the sound is very bad.


I would be curious if my patch changes anything for you:

http://lists.freedesktop.org/archives/spice-devel/2014-September/017334.html

Cheers,

Jeremy
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread nicolas prochazka 
Hello,
I've done  differents tests, with the differents combinaisons between qemu
X and spice-server,
I can say  that is  since video adaptative streaming, the video streaming
is bad compare to the  old version (spice 0.12.3 / qemu 1.7 ).
When i set SPICE_DISABLE_ADAPTIVE_STREAMING=Y , my tests shows that's a lot
of frames are dropping, because of sound synchronisation, The only way to
get good streaming performance is to desactivate audio from client side. (
--spice-disable-audio).

An other point, when you disable streaming detection from server side,
video is good, but the sound is very bad.

Regards,
Nicolas




2014-09-08 16:57 GMT+02:00 Jeremy White :

> On Sat, Sep 06, 2014 at 08:59:47AM -0500, Jeremy White wrote:
>>>
 I think there actually is the same issue when running within QEMU: sound
> is emitted from a QEMU thread:
>

 Is there a bug or someone that is working on that issue?  I'd be
 curious to
 see if my patch resolves the problem for them.

>>>
>>> I've only noticed this through code inspection/gdb breakpoints after you
>>> pointed out the issue you found.  However, I'm fairly sure there has
>>> been reports on this mailing list of sound stopping after a while when
>>> watching a video. This matches very closely what you described.
>>>
>>
>> I was thinking of
>> http://lists.freedesktop.org/archives/spice-devel/2014-July/017132.html
>> Maybe there was another email.
>>
>
> I couldn't quickly figure out the threading arrangement in qemu, but if
> the main channel is being driven by a different thread than the audio
> channel, then I think this patch would have introduced a bug:
>
> ---
> commit bf9e210b21a66210b19f69fcaa4542b393b7dc22
> Author: Yonit Halperin 
> Date:   Fri Jan 25 09:34:19 2013 -0500
>
> red_worker: video streams - adjust client playback latency
>
> --
>
> Of course, that's 18 months ago, so it seems to me we would have found it
> by now (despite it being a subtle, unpredictable bug that only occurs
> during video playback).
>
> But, just to be sure, Nicolas, would you mind setting the
> SPICE_DISABLE_ADAPTIVE_STREAMING environment variable prior to running
> the client and seeing if that changes anything?
>
> Cheers,
>
> Jeremy
>
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread Jeremy White 

On Sat, Sep 06, 2014 at 08:59:47AM -0500, Jeremy White wrote:

I think there actually is the same issue when running within QEMU: sound
is emitted from a QEMU thread:


Is there a bug or someone that is working on that issue?  I'd be curious to
see if my patch resolves the problem for them.


I've only noticed this through code inspection/gdb breakpoints after you
pointed out the issue you found.  However, I'm fairly sure there has
been reports on this mailing list of sound stopping after a while when
watching a video. This matches very closely what you described.


I was thinking of
http://lists.freedesktop.org/archives/spice-devel/2014-July/017132.html
Maybe there was another email.


I couldn't quickly figure out the threading arrangement in qemu, but if 
the main channel is being driven by a different thread than the audio 
channel, then I think this patch would have introduced a bug:


---
commit bf9e210b21a66210b19f69fcaa4542b393b7dc22
Author: Yonit Halperin 
Date:   Fri Jan 25 09:34:19 2013 -0500

red_worker: video streams - adjust client playback latency

--

Of course, that's 18 months ago, so it seems to me we would have found 
it by now (despite it being a subtle, unpredictable bug that only occurs 
during video playback).


But, just to be sure, Nicolas, would you mind setting the 
SPICE_DISABLE_ADAPTIVE_STREAMING environment variable prior to running 
the client and seeing if that changes anything?


Cheers,

Jeremy
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [PATCH 2/9] build-sys: check for spicy-screenshot

2014-09-08 Thread Christophe Fergeau 
On Mon, Nov 18, 2013 at 05:33:38AM -0500, Marc-André Lureau wrote:
> It's an old patch, I should have modified those as well:

Something similar to the initial patch has been pushed as 686750e4

> 
> server/tests/test_multiple.py:parser.add_argument('--client', default='spicy')
> tests/migrate.py:parser.add_argument('--client', dest='client', 
> default='spicy', choices=['spi

This is still there though.

Christophe


pgpCbct6wX_am.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [PATCH 3/9] clean-up: remove unused function

2014-09-08 Thread Christophe Fergeau 
ACK.

On Mon, Nov 18, 2013 at 11:28:27AM +0100, Marc-André Lureau wrote:
> From: Marc-André Lureau 
> 
> ---
>  server/reds.c | 5 -
>  server/reds.h | 1 -
>  2 files changed, 6 deletions(-)
> 
> diff --git a/server/reds.c b/server/reds.c
> index 146dfc7..6197547 100644
> --- a/server/reds.c
> +++ b/server/reds.c
> @@ -3486,11 +3486,6 @@ uint32_t reds_get_mm_time(void)
>  return time_space.tv_sec * 1000 + time_space.tv_nsec / 1000 / 1000;
>  }
>  
> -void reds_update_mm_timer(uint32_t mm_time)
> -{
> -red_dispatcher_set_mm_time(mm_time);
> -}
> -
>  void reds_enable_mm_timer(void)
>  {
>  core->timer_start(reds->mm_timer, MM_TIMER_GRANULARITY_MS);
> diff --git a/server/reds.h b/server/reds.h
> index 1c5ae84..24b4d95 100644
> --- a/server/reds.h
> +++ b/server/reds.h
> @@ -122,7 +122,6 @@ void reds_handle_channel_event(int event, 
> SpiceChannelEventInfo *info);
>  
>  void reds_disable_mm_timer(void);
>  void reds_enable_mm_timer(void);
> -void reds_update_mm_timer(uint32_t mm_time);
>  uint32_t reds_get_mm_time(void);
>  void reds_set_client_mouse_allowed(int is_client_mouse_allowed,
> int x_res, int y_res);
> -- 
> 1.8.3.1
> 
> ___
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel


pgpJgCXAmo0BK.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [PATCH 1/9] reds: lookup corresponding channel id

2014-09-08 Thread Christophe Fergeau 
ACK, but please mention this bug in the commit log.

Christophe

On Thu, Aug 28, 2014 at 04:22:43PM +0200, Marc-André Lureau wrote:
> ping
> 
> this patch solves the assert from bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1058625
> 
> 
> On Mon, Nov 18, 2013 at 11:28 AM, Marc-André Lureau <
> marcandre.lur...@gmail.com> wrote:
> 
> > In reds_send_link_ack(), lookup the channel with the same id as the link
> > message.
> > ---
> >  server/reds.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/server/reds.c b/server/reds.c
> > index 2a0002b..146dfc7 100644
> > --- a/server/reds.c
> > +++ b/server/reds.c
> > @@ -1453,7 +1453,8 @@ static int reds_send_link_ack(RedLinkInfo *link)
> >
> >  ack.error = SPICE_LINK_ERR_OK;
> >
> > -channel = reds_find_channel(link->link_mess->channel_type, 0);
> > +channel = reds_find_channel(link->link_mess->channel_type,
> > +link->link_mess->channel_id);
> >  if (!channel) {
> >  spice_assert(link->link_mess->channel_type == SPICE_CHANNEL_MAIN);
> >  spice_assert(reds->main_channel);
> > --
> > 1.8.3.1
> >
> >
> 
> 
> -- 
> Marc-André Lureau

> ___
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel



pgpaWXYgsQguV.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread Christophe Fergeau 
On Mon, Sep 08, 2014 at 11:26:58AM +0200, Christophe Fergeau wrote:
> Hey,
> 
> On Sat, Sep 06, 2014 at 08:59:47AM -0500, Jeremy White wrote:
> > >I think there actually is the same issue when running within QEMU: sound
> > >is emitted from a QEMU thread:
> > 
> > Is there a bug or someone that is working on that issue?  I'd be curious to
> > see if my patch resolves the problem for them.
> 
> I've only noticed this through code inspection/gdb breakpoints after you
> pointed out the issue you found.  However, I'm fairly sure there has
> been reports on this mailing list of sound stopping after a while when
> watching a video. This matches very closely what you described.

I was thinking of
http://lists.freedesktop.org/archives/spice-devel/2014-July/017132.html
Maybe there was another email.

Christophe


pgpE_NrynqVVF.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [vdagent-linux 1/2] randr: remove monitors.xml on auto-configuration

2014-09-08 Thread Marc-André Lureau 
ping


On Wed, Aug 27, 2014 at 7:22 PM, Marc-André Lureau <
marcandre.lur...@redhat.com> wrote:

> From: Marc-Andre Lureau 
>
> GNOME will restore monitors.xml configuration whenever the timestamp
> "config > change". The "change" timestamp is the last user applied
> configuration, whereas the "config" timestamp is updated when
> the screen is updated or ouput/crtc modes are added/removed.
>
> These condition are triggered by vdagent during monitor config. Since we
> can't control the timestamps (playing with delay will be inherently
> event more racy), the only sane way I can think of is to disable gsd
> behaviour. This can be achieved by deleting the ~/.config/monitors.xml,
> which is the intended configuration to restore, so vdagent will override
> whatever configuration was saved previously.
>
> Somehow, if vdagent would be better integrated with gnome2, it would use
> the gnome-rr and/or org.gnome.SettingsDaemon.XRANDR dbus
> API. Thanksfully, in gnome3, the monitor auto-configuration has been
> merged in.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1086657
> ---
>  src/vdagent-x11-randr.c | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/src/vdagent-x11-randr.c b/src/vdagent-x11-randr.c
> index 46367bc..5faaee6 100644
> --- a/src/vdagent-x11-randr.c
> +++ b/src/vdagent-x11-randr.c
> @@ -21,6 +21,7 @@
>  along with this program.  If not, see .
>  */
>
> +#include 
>  #include 
>  #include 
>  #include 
> @@ -745,6 +746,10 @@ void vdagent_x11_set_monitor_config(struct
> vdagent_x11 *x11,
>  goto exit;
>  }
>
> +gchar *config = g_build_filename (g_get_user_config_dir (),
> "monitors.xml", NULL);
> +g_unlink(config);
> +g_free(config);
> +
>  for (i = mon_config->num_of_monitors; i < x11->randr.res->noutput;
> i++)
>  xrandr_disable_output(x11, i);
>
> --
> 1.9.3
>
> ___
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>



-- 
Marc-André Lureau
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [vdagent-linux v2] randr: handle XRRScreenChangeNotifyEvent

2014-09-08 Thread Marc-André Lureau 
ping


On Wed, Aug 27, 2014 at 8:51 PM, Marc-André Lureau <
marcandre.lur...@redhat.com> wrote:

> From: Marc-Andre Lureau 
>
> Make sure vdagent follows the current monitor configuration.  This
> solves a number of issue where the pointer input is off, because the
> uinput tablet isn't reconfigured.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1086657
> ---
>  src/vdagent-x11-priv.h  |  4 +++-
>  src/vdagent-x11-randr.c | 34 +-
>  src/vdagent-x11.c   |  4 +++-
>  3 files changed, 39 insertions(+), 3 deletions(-)
>
> diff --git a/src/vdagent-x11-priv.h b/src/vdagent-x11-priv.h
> index 38f852e..d60cc07 100644
> --- a/src/vdagent-x11-priv.h
> +++ b/src/vdagent-x11-priv.h
> @@ -95,6 +95,7 @@ struct vdagent_x11 {
>  int height[MAX_SCREENS];
>  int has_xfixes;
>  int xfixes_event_base;
> +int xrandr_event_base;
>  int max_prop_size;
>  int expected_targets_notifies[256];
>  int clipboard_owner[256];
> @@ -145,7 +146,8 @@ void vdagent_x11_send_daemon_guest_xorg_res(struct
> vdagent_x11 *x11,
>  int update);
>  void vdagent_x11_randr_handle_root_size_change(struct vdagent_x11 *x11,
>  int screen, int width, int
> height);
> -
> +int vdagent_x11_randr_handle_event(struct vdagent_x11 *x11,
> +XEvent event);
>  void vdagent_x11_set_error_handler(struct vdagent_x11 *x11,
>  int (*handler)(Display *, XErrorEvent *));
>  int vdagent_x11_restore_error_handler(struct vdagent_x11 *x11);
> diff --git a/src/vdagent-x11-randr.c b/src/vdagent-x11-randr.c
> index 5faaee6..c6f790e 100644
> --- a/src/vdagent-x11-randr.c
> +++ b/src/vdagent-x11-randr.c
> @@ -132,12 +132,15 @@ void vdagent_x11_randr_init(struct vdagent_x11 *x11)
>  return;
>  }
>
> -if (XRRQueryExtension(x11->display, &i, &i)) {
> +if (XRRQueryExtension(x11->display, &x11->xrandr_event_base, &i)) {
>  XRRQueryVersion(x11->display, &x11->xrandr_major,
> &x11->xrandr_minor);
>  if (x11->xrandr_major == 1 && x11->xrandr_minor >= 3)
>  x11->has_xrandr = 1;
>  }
>
> +XRRSelectInput(x11->display, x11->root_window[0],
> +RRScreenChangeNotifyMask | RRCrtcChangeNotifyMask);
> +
>  if (x11->has_xrandr) {
>  update_randr_res(x11, 0);
>  } else {
> @@ -466,6 +469,8 @@ static int set_screen_to_best_size(struct vdagent_x11
> *x11, int width, int heigh
>  void vdagent_x11_randr_handle_root_size_change(struct vdagent_x11 *x11,
>  int screen, int width, int height)
>  {
> +update_randr_res(x11, 0);
> +
>  if (width == x11->width[screen] && height == x11->height[screen]) {
>  return;
>  }
> @@ -481,6 +486,33 @@ void vdagent_x11_randr_handle_root_size_change(struct
> vdagent_x11 *x11,
>  }
>  }
>
> +int vdagent_x11_randr_handle_event(struct vdagent_x11 *x11,
> +XEvent event)
> +{
> +int handled = TRUE;
> +
> +switch (event.type - x11->xrandr_event_base) {
> +case RRScreenChangeNotify: {
> +XRRScreenChangeNotifyEvent *sce =
> +(XRRScreenChangeNotifyEvent *) &event;
> +vdagent_x11_randr_handle_root_size_change(x11, 0,
> +sce->width, sce->height);
> +break;
> +}
> +case RRNotify: {
> +update_randr_res(x11, 0);
> +if (!x11->dont_send_guest_xorg_res)
> +vdagent_x11_send_daemon_guest_xorg_res(x11, 1);
> +break;
> +}
> +default:
> +handled = FALSE;
> +break;
> +}
> +
> +return handled;
> +}
> +
>  static int min_int(int x, int y)
>  {
>  return x > y ? y : x;
> diff --git a/src/vdagent-x11.c b/src/vdagent-x11.c
> index 752b337..9619dc5 100644
> --- a/src/vdagent-x11.c
> +++ b/src/vdagent-x11.c
> @@ -503,9 +503,11 @@ static void vdagent_x11_handle_event(struct
> vdagent_x11 *x11, XEvent event)
>  return;
>  }
>
> +if (vdagent_x11_randr_handle_event(x11, event))
> +return;
> +
>  switch (event.type) {
>  case ConfigureNotify:
> -// TODO: handle CrtcConfigureNotify, OutputConfigureNotify can be
> ignored.
>  for (i = 0; i < x11->screen_count; i++)
>  if (event.xconfigure.window == x11->root_window[i])
>  break;
> --
> 1.9.3
>
> ___
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>



-- 
Marc-André Lureau
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Help with solving a thread safety issue

2014-09-08 Thread Christophe Fergeau 
Hey,

On Sat, Sep 06, 2014 at 08:59:47AM -0500, Jeremy White wrote:
> >I think there actually is the same issue when running within QEMU: sound
> >is emitted from a QEMU thread:
> 
> Is there a bug or someone that is working on that issue?  I'd be curious to
> see if my patch resolves the problem for them.

I've only noticed this through code inspection/gdb breakpoints after you
pointed out the issue you found.  However, I'm fairly sure there has
been reports on this mailing list of sound stopping after a while when
watching a video. This matches very closely what you described.

Christophe


pgpHcAMjbxpGA.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] [vdagent-linux] data: remove rsyslog config files

2014-09-08 Thread Christophe Fergeau 
Hey,

Yup, makes sense to me, though I can't parse the commit log. A short
"It's possible to filter spice-vdagent/spice-vdagentd log messages out
of /var/log/messages with
journalctl SYSLOG_IDENTIFIER=spice-vdagent SYSLOG_IDENTIFIER=spice-vdagentd"
would do.
ACK, and hopefully we will get bug reports if someone needs the rsyslog
file on a journalctl-less system.

Christophe

On Fri, Sep 05, 2014 at 03:18:38PM +0200, Marc-André Lureau wrote:
> Many systems don't use rsyslog, others don't need seperate syslog files
> for vdagent.  Instead, /var/log/messages can be grep for spice-vdagent,
> or system with the journal can call journalctl
> SYSLOG_IDENTIFIER=spice-vdagent.
> 
> This simplify spice-vdagent packaging and updates, since there are no
> config files to deal with.
> 
> Related:
> https://bugzilla.redhat.com/show_bug.cgi?id=1136881
> ---
>  Makefile.am| 4 
>  data/rsyslog.d/spice-vdagentd.conf | 4 
>  2 files changed, 8 deletions(-)
>  delete mode 100644 data/rsyslog.d/spice-vdagentd.conf
> 
> diff --git a/Makefile.am b/Makefile.am
> index 7fae742..510f460 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -51,9 +51,6 @@ gdmautostart2_DATA = 
> $(top_srcdir)/data/spice-vdagent.desktop
>  install-data-local:
>   $(mkdir_p) $(DESTDIR)$(localstatedir)/run/spice-vdagentd
>  
> -rsyslogdir = $(sysconfdir)/rsyslog.d
> -rsyslog_DATA = $(top_srcdir)/data/rsyslog.d/spice-vdagentd.conf
> -
>  if INIT_SCRIPT_RED_HAT
>  initdir = $(sysconfdir)/rc.d/init.d
>  init_SCRIPTS = $(top_srcdir)/data/spice-vdagentd
> @@ -79,7 +76,6 @@ manpage_DATA = data/spice-vdagent.1 \
>  EXTRA_DIST = \
>   README.RHEL-5   \
>   data/70-spice-vdagentd.rules\
> - data/rsyslog.d/spice-vdagentd.conf  \
>   data/spice-vdagent.desktop  \
>   data/spice-vdagentd \
>   data/spice-vdagentd.service \
> diff --git a/data/rsyslog.d/spice-vdagentd.conf 
> b/data/rsyslog.d/spice-vdagentd.conf
> deleted file mode 100644
> index 2437ba0..000
> --- a/data/rsyslog.d/spice-vdagentd.conf
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -# A template to for higher precision timestamps + severity logging
> -$template SpiceTmpl,"%TIMESTAMP%.%TIMESTAMP:::date-subseconds% %syslogtag% 
> %syslogseverity-text%:%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n"
> -
> -:programname, startswith, "spice-vdagent"
> /var/log/spice-vdagent.log;SpiceTmpl
> -- 
> 1.9.3
> 
> ___
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel


pgpfmgPiBwxV4.pgp
Description: PGP signature
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel