qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] sdl2: add opengl rendering support
Date: Thu, 11 Dec 2014 14:28:33 +0100	[thread overview]
Message-ID: <54899C01.9050503@redhat.com> (raw)
In-Reply-To: <1418295956-22479-1-git-send-email-kraxel@redhat.com>



On 11/12/2014 12:05, Gerd Hoffmann wrote:
>   Hi,
> 
> This series add support for screen rendering using opengl.  This only
> blits classic DisplaySurfaces to the screen using opengl, it does not
> (yet) enable gfx emulation use opengl for rendering.
> 
> It depends on the "sdl2: fixes, cleanups and opengl preparation"
> series just posted.
> 
> The big question mark (and the reason this is RfC) is how we are going
> to enable/disable opengl at runtime.  The options I see are:
> 
>  (1) make that a ui option, i.e. '-display sdl,opengl={on,off}'.
>  (2) make that a global option, i.e. -opengl={on,off}
> 
> I'd tend to go for (2).
> 
> First, because we have a initialization order issue once gfx emulation
> starts using opengl:  ui code is initialized after device code (and this
> can't be changed easily because devices need register displays before we
> init the ui).  Therefore with (1) the device emulation doesn't know at
> init time time whenever opengl is available or not.

Do you have a case in mind where the device emulation needs to know that?
As opposed to "always need opengl" or "never needs opengl".

If not, the semantics of (1) are easy to describe, though maybe not to
implement:

   device request        backend support     result
     no                    no                  no
     no                    yes                 yes
     no                    unspecified         no or yes, depends on backend
     yes                   no                  error
     yes                   yes                 yes
     yes                   unspecified         error or yes, depends on backend

> Second for the long term there will be 3d support in a number of UIs:
> I expect sdl2, gtk, egl (using render nodes, for headless) and spice.
> Having a global switch for them all looks easier.

But you'd still need to know the UI in order to have a decent default.  For
example should "-display vnc" should disable opengl by default (it's not
in your list above)?  "-display egl" probably should enable it.

Perhaps "-display" could be processed in two steps.

Paolo

  parent reply	other threads:[~2014-12-11 13:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:05 [Qemu-devel] [RfC PATCH 0/3] sdl2: add opengl rendering support Gerd Hoffmann
2014-12-11 11:05 ` [Qemu-devel] [RfC PATCH 1/3] configure: opengl overhaul Gerd Hoffmann
2014-12-15 16:46   ` Michael Walle
2014-12-16  9:37     ` Gerd Hoffmann
2014-12-11 11:05 ` [Qemu-devel] [RfC PATCH 2/3] sdl2: add support for display rendering using opengl Gerd Hoffmann
2014-12-11 15:57   ` Max Reitz
2014-12-12 11:04     ` Gerd Hoffmann
2014-12-12 13:34       ` Max Reitz
2015-01-12 12:46         ` Gerd Hoffmann
2015-01-15 11:15           ` Gerd Hoffmann
2015-01-15 12:17             ` Paolo Bonzini
2015-01-15 12:23               ` Peter Maydell
2015-01-15 14:30                 ` Gerd Hoffmann
2015-01-15 16:49           ` Max Reitz
2014-12-11 11:05 ` [Qemu-devel] [RfC PATCH 3/3] sdl2: move SDL_* includes to sdl2.h Gerd Hoffmann
2014-12-11 12:32 ` [Qemu-devel] [RfC PATCH 0/3] sdl2: add opengl rendering support Daniel P. Berrange
2014-12-11 15:29   ` Gerd Hoffmann
2014-12-11 15:46     ` Daniel P. Berrange
2014-12-11 15:54       ` Gerd Hoffmann
2014-12-11 13:28 ` Paolo Bonzini [this message]
2014-12-11 15:40   ` Gerd Hoffmann
2014-12-11 17:25     ` Paolo Bonzini

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=54899C01.9050503@redhat.com \
    --to=pbonzini@redhat.com \
    --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).