From: Erico Nunes <ernunes@redhat.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
Cc: kraxel@redhat.com, marcandre.lureau@redhat.com,
akihiko.odaki@gmail.com, dmitry.osipenko@collabora.com,
ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com,
hi@alyssa.is
Subject: Re: [PATCH v3 0/9] gfxstream + rutabaga_gfx
Date: Mon, 7 Aug 2023 16:24:07 +0200 [thread overview]
Message-ID: <b9dc2c50-00cf-12ae-d1c9-cb31d089a24d@redhat.com> (raw)
In-Reply-To: <20230803235502.373-1-gurchetansingh@google.com>
Hello,
On 04/08/2023 01:54, Gurchetan Singh wrote:
> Prior versions:
>
> https://lists.gnu.org/archive/html/qemu-devel/2023-07/msg05801.html
>
> https://lists.gnu.org/archive/html/qemu-devel/2023-07/msg02341.html
>
> https://patchew.org/QEMU/20230421011223.718-1-gurchetansingh@chromium.org/
>
> Changes since v2:
> - Incorporated review feedback
>
> How to build both rutabaga and gfxstream guest/host libs:
>
> https://crosvm.dev/book/appendix/rutabaga_gfx.html
>
> Branch containing this patch series:
>
> https://gitlab.freedesktop.org/gurchetansingh/qemu-gfxstream/-/commits/qemu-gfxstream-v3
I tried this on Fedora with a Fedora guest and I was able to get Vulkan
headless applications as well as Wayland proxy with sommelier to work.
If you don't mind, I have a few questions.
I was not able to run Vulkan applications over the Wayland proxy, only
unaccelerated apps. This seems to be unsupported yet; is actually
unsupported for now or was something missing in my setup?
Also apparently GL/GLES is only supported on Android right now as you
mentioned, since on Linux the gfxstream guest only installs the Vulkan
library and icd. What is the plan to support GL on Linux; provide
gfxstream GL guest libraries later or enable Zink or some other solution?
Then if I understand correctly, Mesa virgl is not used at all with the
gfxstream solution, so I guess we would need to find a way to ship the
gfxstream guest libraries too on distributions?
Also I wonder about including all of the the dependencies required to
get this to build on distributions as well to enable the feature on
distribution-provided qemu, but I guess we can figure this out later...
And finally out of curiosity, I see that rutabaga also has a
virgl_renderer (and virgl_renderer_next) backend which would then not
use gfxstream but virglrenderer instead. I wonder if there would be any
benefit/features in enabling that with qemu later compared to the
current qemu virtio/virglrenderer implementation (if that would make
sense at all)?
Thanks
Erico
next prev parent reply other threads:[~2023-08-07 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 23:54 [PATCH v3 0/9] gfxstream + rutabaga_gfx Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-08-03 23:54 ` [PATCH v3 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-08-04 7:31 ` Akihiko Odaki
2023-08-03 23:55 ` [PATCH v3 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-08-03 23:55 ` [PATCH v3 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-08-03 23:55 ` [PATCH v3 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2023-08-04 7:36 ` Akihiko Odaki
2023-08-07 14:24 ` Erico Nunes [this message]
2023-08-09 1:50 ` [PATCH v3 0/9] gfxstream + rutabaga_gfx Gurchetan Singh
2023-08-09 2:17 ` Huang Rui
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=b9dc2c50-00cf-12ae-d1c9-cb31d089a24d@redhat.com \
--to=ernunes@redhat.com \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=hi@alyssa.is \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=shentey@gmail.com \
/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).