From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] virgl: add SDL support and enable by default
Date: Sun, 1 Sep 2019 22:36:30 +0200 [thread overview]
Message-ID: <cover.1567369258.git.alex.kanavin@gmail.com> (raw)
This patchset adds two enhancements to qemu virgl support (which is
a virtualized accelerated 3D graphics support for the qemu guests):
1. SDL qemu frontend now comes with virgl fully enabled and working
(over ssh X11 forwarding as well!), so using the gtk frontend
is no longer necessary. 'oe-selftest' is adjusted to test both
frontends.
2. virgl itself is enabled by default in qemu, when 'opengl' is in
DISTRO_FEATURES. This pulls in a few components during build (particularly,
libdrm, virglrenderer and a special minimal configuration of mesa-native).
I tested the impact on build times: it is about 25-30 seconds on a 16 core
machine. 'bitbake core-image-minimal' goes from 26m45 to 27m13.
Gtk qemu frontend remains disabled by default, as it adds more to the build times.
The following changes since commit 270bd86740a080fb56d932a5c0eb70d6ce2a2b3c:
libepoxy: enable x11 PACKAGECONFIG for native/nativesdk (2019-09-01 17:08:18 +0200)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib akanavin/qemu-split-virgl-gtk
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/qemu-split-virgl-gtk
Alexander Kanavin (5):
bitbake.conf: propagate 'opengl' DISTRO_FEATURE to native/nativesdk
from target
libsdl2: enable opengl option for native/nativesdk, subject to
'opengl' in DISTRO_FEATURES
qemu: enable virglrenderer and glx options subject to 'opengl'
DISTRO_FEATURE
runqemu: add options that enable virgl with the SDL frontend
oe-selftest: extend virgl gtk test to also check the SDL option
meta/conf/bitbake.conf | 4 +--
meta/lib/oeqa/selftest/cases/runtime_test.py | 29 ++++++++++---------
.../qemu/qemu-system-native_4.1.0.bb | 4 ++-
meta/recipes-devtools/qemu/qemu_4.1.0.bb | 5 +++-
meta/recipes-gnome/gtk+/gtk+3.inc | 2 ++
meta/recipes-graphics/cairo/cairo_1.16.0.bb | 2 ++
.../libepoxy/libepoxy_1.5.3.bb | 2 --
.../libsdl2/libsdl2_2.0.10.bb | 4 +--
.../virglrenderer/virglrenderer_0.8.0.bb | 2 --
scripts/runqemu | 15 ++++++++--
10 files changed, 43 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2019-09-01 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 20:36 Alexander Kanavin [this message]
2019-09-01 20:36 ` [PATCH 1/5] bitbake.conf: propagate 'opengl' DISTRO_FEATURE to native/nativesdk from target Alexander Kanavin
2019-09-01 20:36 ` [PATCH 2/5] libsdl2: enable opengl option for native/nativesdk, subject to 'opengl' in DISTRO_FEATURES Alexander Kanavin
2019-09-01 20:36 ` [PATCH 3/5] qemu: enable virglrenderer and glx options subject to 'opengl' DISTRO_FEATURE Alexander Kanavin
2019-09-01 20:36 ` [PATCH 4/5] runqemu: add options that enable virgl with the SDL frontend Alexander Kanavin
2019-09-01 20:36 ` [PATCH 5/5] oe-selftest: extend virgl gtk test to also check the SDL option Alexander Kanavin
2019-09-01 21:02 ` ✗ patchtest: failure for virgl: add SDL support and enable by default Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 11:18 [PATCH 0/5] " Alexander Kanavin
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=cover.1567369258.git.alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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