From: Cole Robinson <crobinso@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] virtio-gpu: Warn if UI config will disable virgl
Date: Fri, 20 May 2016 10:49:40 -0400 [thread overview]
Message-ID: <fc47f4a7-d756-7de1-c523-45ee39550876@redhat.com> (raw)
In-Reply-To: <1463723606.3526.7.camel@redhat.com>
On 05/20/2016 01:53 AM, Gerd Hoffmann wrote:
> On Mi, 2016-05-18 at 12:40 -0400, Cole Robinson wrote:
>> Give users a hint if their config is wrong.
>>
>> Signed-off-by: Cole Robinson <crobinso@redhat.com>
>> ---
>> If virgl support is built into qemu, virgl=on is the default, so this
>> could be noisy in cases where people don't even care about virgl. So
>> I won't object if this is dropped.
>
> Yes, it's enabled by default, so users have to flip one switch only
> (-spice gl=on) to enable 3d, not two. So warning here is a bad thing
> IMO.
>
> We could turn the virgl switch into tristate (OnOffAuto), have it
> default to Auto, then fail (not warn) in case it is set to On without 3d
> support being available.
>
Property settings are part of the migration format, right? Is there an easy
way to change the 'virgl' property like that in a backwards compatible way? Or
decouple the command line handling from the Property value?
Thanks,
Cole
next prev parent reply other threads:[~2016-05-20 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:40 [Qemu-devel] [PATCH 0/3] ui: improve feedback if gl setup fails Cole Robinson
2016-05-18 16:40 ` [Qemu-devel] [PATCH 1/3] ui: egl: Replace fprintf with error_report Cole Robinson
2016-05-18 16:50 ` Eric Blake
2016-05-19 15:19 ` Marc-André Lureau
2016-05-18 16:40 ` [Qemu-devel] [PATCH 2/3] ui: spice: Exit if gl=on EGL init fails Cole Robinson
2016-05-19 15:19 ` Marc-André Lureau
2016-05-18 16:40 ` [Qemu-devel] [PATCH 3/3] virtio-gpu: Warn if UI config will disable virgl Cole Robinson
2016-05-19 15:19 ` Marc-André Lureau
2016-05-20 5:53 ` Gerd Hoffmann
2016-05-20 14:49 ` Cole Robinson [this message]
2016-05-23 7:34 ` Gerd Hoffmann
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=fc47f4a7-d756-7de1-c523-45ee39550876@redhat.com \
--to=crobinso@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@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).