From: Gerd Hoffmann <kraxel@redhat.com>
To: Joe Kniss <djmk@google.com>
Cc: qemu-devel@nongnu.org, Dave Airlie <airlied@redhat.com>
Subject: Re: [Qemu-devel] qemu+virgl on systems without dmabuf and/or GBM
Date: Tue, 14 Nov 2017 08:05:58 +0100 [thread overview]
Message-ID: <20171114070558.kydby4zt5hhnser4@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAOvnNvYpQSdM5PXoBZXwf6op+FVNd3j0CPBnKGqxfa2V3pnJjA@mail.gmail.com>
On Mon, Nov 13, 2017 at 04:15:30PM -0800, Joe Kniss wrote:
> Hi,
>
> I am developing using qemu with virglrenderer on linux systems that
> do not support dmabufs or GBM. I have been successful making this
> work using glx and ignoring egl/dmabuf/gbm use in qemu.
nvidia?
Which user interface?
> Unfortunately, there is currently no way to configure qemu to use
> opengl but disable egl/dmabuf/gbm.
Wrong. dmabuf support is purely optional. And egl is required (at
runtime) only in case qemu creates the opengl context by itself. qemu
happily uses opengl contexts created by sdl2 or gtk (3.16+ GtkGlArea)
even if they are glx contexts. dmabuf sharing obviously doesn't work
then, but you don't need that for virgl + local display.
> 1) Check for gbm in configure, if it is unavailable disable ui/egl*
> since this egl implementation depends on gbm.
> 2) Check for gbm in configure, modify ui/egl* to work when gbm is missing.
> 3) Add disable-egl flag to configure, ignore gbm package when egl is disabled.
I don't think any of this is needed. Also this should be decided at
runtime not compile time.
cheers,
Gerd
prev parent reply other threads:[~2017-11-14 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 0:15 [Qemu-devel] qemu+virgl on systems without dmabuf and/or GBM Joe Kniss
2017-11-14 2:37 ` David Airlie
2017-11-14 7:05 ` Gerd Hoffmann [this message]
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=20171114070558.kydby4zt5hhnser4@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=djmk@google.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).