qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Frediano Ziglio <fziglio@redhat.com>
Cc: spice-devel@lists.freedesktop.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] RFC: qxl: allow to specify head limit to qxl driver
Date: Thu, 11 Jun 2015 12:10:57 +0200	[thread overview]
Message-ID: <1434017457.27114.34.camel@redhat.com> (raw)
In-Reply-To: <1434015506-6955-1-git-send-email-fziglio@redhat.com>

On Do, 2015-06-11 at 10:38 +0100, Frediano Ziglio wrote:
> libvirt has this as a video card parameter (actually set to 1 but not
> used). This parameter will allow to limit setting a use can do (which
> could be confusing).

Hmm.  So heads is '1' by default but ignored today.  When this starts to
be actually applied that will break existing multihead setups I suspect.

> This patch rely on some change in spice-protocol which are not still
> accepted. See
> http://lists.freedesktop.org/archives/spice-devel/2015-June/020221.html.

Spice-server changes, right?
Needs #ifdefs so qemu continues to build with old spice-server versions.
The spice-server changes need to be upstream first.

Also: when we pass on the limit to spice-server anyway spice-server can
take care to apply the limit both ways and not call the
->client_monitors_config() callback with more than $limit monitors.  Has
the advantage to reduce the test matrix:  Limit either works or doesn't.
There will be no spice-server/qemu version combination where the limit
is applied one way only.

  Gerd

  reply	other threads:[~2015-06-11 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  9:38 [Qemu-devel] [PATCH v2] RFC: qxl: allow to specify head limit to qxl driver Frediano Ziglio
2015-06-11 10:10 ` Gerd Hoffmann [this message]
2015-06-12 14:02   ` Frediano Ziglio

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=1434017457.27114.34.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=fziglio@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.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).