From: Gurchetan Singh <gurchetansingh@chromium.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Huang Rui" <ray.huang@amd.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gert Wollny" <gert.wollny@collabora.com>,
qemu-devel@nongnu.org, "Alyssa Ross" <hi@alyssa.is>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Stefano Stabellini" <stefano.stabellini@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Xenia Ragiadakou" <xenia.ragiadakou@amd.com>,
"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
"Honglei Huang" <honglei1.huang@amd.com>,
"Julia Zhang" <julia.zhang@amd.com>,
"Chen Jiqian" <Jiqian.Chen@amd.com>,
"Rob Clark" <robdclark@gmail.com>,
"Yiwei Zhang" <zzyiwei@chromium.org>,
"Sergio Lopez Pascual" <slp@redhat.com>
Subject: Re: [PATCH v6 10/10] docs/system: virtio-gpu: Document host/guest requirements
Date: Tue, 28 Jan 2025 17:18:59 -0800 [thread overview]
Message-ID: <CAAfnVBmrCSk-TBMD7NnVkHtHf9mECMtmxg=ExZF5WZs1mtmqPg@mail.gmail.com> (raw)
In-Reply-To: <20250126201121.470990-11-dmitry.osipenko@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 6215 bytes --]
On Sun, Jan 26, 2025 at 12:14 PM Dmitry Osipenko <
dmitry.osipenko@collabora.com> wrote:
> From: Alex Bennée <alex.bennee@linaro.org>
>
> This attempts to tidy up the VirtIO GPU documentation to make the list
> of requirements clearer. There are still a lot of moving parts and the
> distros have some catching up to do before this is all handled
> automatically.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Sergio Lopez Pascual <slp@redhat.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> [dmitry.osipenko@collabora.com: Extended and corrected doc]
> ---
> docs/system/devices/virtio-gpu.rst | 107 ++++++++++++++++++++++++++++-
> 1 file changed, 106 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/devices/virtio-gpu.rst
> b/docs/system/devices/virtio-gpu.rst
> index ea3eb052df3c..b3db984ff2d3 100644
> --- a/docs/system/devices/virtio-gpu.rst
> +++ b/docs/system/devices/virtio-gpu.rst
> @@ -5,7 +5,9 @@ virtio-gpu
> ==========
>
> This document explains the setup and usage of the virtio-gpu device.
> -The virtio-gpu device paravirtualizes the GPU and display controller.
> +The virtio-gpu device provides a GPU and display controller
> +paravirtualized using VirtIO. It supports a number of different modes
> +from simple 2D displays to fully accelerated 3D graphics.
>
> Linux kernel support
> --------------------
> @@ -13,6 +15,24 @@ Linux kernel support
> virtio-gpu requires a guest Linux kernel built with the
> ``CONFIG_DRM_VIRTIO_GPU`` option.
>
> +Dependencies
> +............
> +
> +.. note::
> + GPU virtualisation is still an evolving field. Depending on the mode
> + you are running you may need to override distribution supplied
> + libraries with more recent versions or enable build options.
> +
> + Depending on the mode there are a number of requirements the host must
> + meet to be able to be able to support guests. For 3D acceleration QEMU
> + must be able to access the hosts GPU and for the best performance be
> + able to reliably share GPU memory with the guest.
> +
> + Virtio-gpu requires a guest Linux kernel built with the
> + ``CONFIG_DRM_VIRTIO_GPU`` option. For 3D accelerations you
> + will need support from guest Mesa configured for whichever encapsulation
> + you need.
> +
> QEMU virtio-gpu variants
> ------------------------
>
> @@ -56,6 +76,16 @@ on typical modern Linux distributions.
> .. _Mesa: https://www.mesa3d.org/
> .. _SwiftShader: https://github.com/google/swiftshader
>
> +.. list-table:: Host Requirements
> + :header-rows: 1
> +
> + * - Mode
> + - Kernel
> + - Userspace
> + * - virtio-gpu
> + - Framebuffer enabled
> + - GTK or SDL display
> +
> virtio-gpu virglrenderer
> ------------------------
>
> @@ -94,6 +124,61 @@ of virtio-gpu host memory window. This is typically
> between 256M and 8G.
>
> .. _drm:
> https://gitlab.freedesktop.org/virgl/virglrenderer/-/tree/main/src/drm
>
> +.. list-table:: Host Requirements
> + :header-rows: 1
> +
> + * - Mode
> + - Kernel
> + - Userspace
> + * - virtio-gpu-gl (OpenGL pass-through)
> + - GPU enabled
> + - libvirglrenderer (virgl support)
> + * - virtio-gpu-gl (Vulkan pass-through)
> + - Linux 6.13+
> + - libvirglrenderer (>= 1.0.0, venus support)
> + * - virtio-gpu-gl (vDRM native context/AMD)
> + - Linux 6.13+
> + - libvirglrenderer (>= 1.1.0, DRM renderer support)
> + * - virtio-gpu-gl (vDRM native context/Freedreno)
> + - Linux 6.4+
> + - libvirglrenderer (>= 1.0.0, DRM renderer support)
> + * - virtio-gpu-gl (vDRM native context/Intel i915)
> + - Linux 6.13+
> + - libvirglrenderer (`mr1384`_, DRM renderer support)
> + * - virtio-gpu-gl (vDRM native context/Asahi)
> + - Linux 6.13+
> + - libvirglrenderer (`mr1274`_, DRM renderer support)
> +
> +.. _mr1384:
> https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1384
> +.. _mr1274:
> https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1274
> +
> +.. list-table:: Guest Requirements
> + :header-rows: 1
> +
> + * - Mode
> + - Mesa Version
> + - Mesa build flags
> + * - virtio-gpu-gl (OpenGL pass-through)
> + - 20.3.0+
> + - -Dgallium-drivers=virgl
> + * - virtio-gpu-gl (Vulkan pass-through)
> + - 24.2.0+
> + - -Dvulkan-drivers=virtio
> + * - virtio-gpu-gl (vDRM native context/AMD)
> + - 25.0.0+
> + - -Dgallium-drivers=radeonsi -Dvulkan-drivers=amd -Damdgpu-virtio=true
> + * - virtio-gpu-gl (vDRM native context/Freedreno)
> + - 23.1.0+
> + - -Dgallium-drivers=freedreno -Dvulkan-drivers=freedreno
> + * - virtio-gpu-gl (vDRM native context/Intel i915)
> + - `mr29870`_
> + - -Dgallium-drivers=iris -Dvulkan-drivers=intel
> -Dintel-virtio-experimental=true
> + * - virtio-gpu-gl (vDRM native context/Asahi)
> + - 24.2.0+
> + - -Dgallium-drivers=asahi -Dvulkan-drivers=asahi
> +
> +.. _mr29870:
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29870
> +
> virtio-gpu rutabaga
> -------------------
>
> @@ -133,3 +218,23 @@ Surfaceless is the default if ``wsi`` is not
> specified.
> .. _Wayland display passthrough:
> https://www.youtube.com/watch?v=OZJiHMtIQ2M
> .. _gfxstream-enabled rutabaga:
> https://crosvm.dev/book/appendix/rutabaga_gfx.html
> .. _guest Wayland proxy: https://crosvm.dev/book/devices/wayland.html
> +
> +.. list-table:: Host Requirements
> + :header-rows: 1
> +
> + * - Mode
> + - Kernel
> + - Userspace
> + * - virtio-gpu-gl (rutabaga/gfxstream)
> + - GPU enabled
> + - aemu/rutabaga_gfx_ffi or vhost-user client with support
> +
> +.. list-table:: Guest Requirements
> + :header-rows: 1
> +
> + * - Mode
> + - Mesa Version
> + - Mesa build flags
> + * - virtio-gpu-gl (rutabaga/gfxstream)
>
Shouldn't this be `virtio-gpu-rutabaga` instead of `virtio-gpu-gl`? If
we're including WiP MRs, can we include Magma too??
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33190
> + - 24.3.0+
> + - -Dvulkan-drivers=gfxstream
> --
> 2.47.1
>
>
[-- Attachment #2: Type: text/html, Size: 8516 bytes --]
next prev parent reply other threads:[~2025-01-29 1:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 20:11 [PATCH v6 00/10] Support virtio-gpu DRM native context Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 01/10] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 02/10] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 03/10] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 04/10] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2025-01-27 16:18 ` Alex Bennée
2025-01-26 20:11 ` [PATCH v6 05/10] virtio-gpu: Support DRM native context Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 06/10] ui/sdl2: Don't disable scanout when display is refreshed Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 07/10] ui/gtk: " Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 08/10] docs/system: virtio-gpu: Add link to Mesa VirGL doc Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 09/10] docs/system: virtio-gpu: Update Venus link Dmitry Osipenko
2025-01-26 20:11 ` [PATCH v6 10/10] docs/system: virtio-gpu: Document host/guest requirements Dmitry Osipenko
2025-01-27 6:28 ` Akihiko Odaki
2025-01-27 9:45 ` Alex Bennée
2025-01-28 6:20 ` Akihiko Odaki
2025-01-31 17:17 ` Dmitry Osipenko
2025-01-29 1:18 ` Gurchetan Singh [this message]
2025-01-31 17:19 ` Dmitry Osipenko
2025-02-02 22:16 ` Dmitry Osipenko
2025-01-27 16:17 ` [PATCH v6 00/10] Support virtio-gpu DRM native context Alex Bennée
2025-01-31 17:13 ` Dmitry Osipenko
2025-02-17 15:18 ` Alex Bennée
2025-02-02 15:17 ` Dmitry Osipenko
2025-02-03 9:07 ` Alex Bennée
2025-02-03 18:15 ` Kim, Dongwon
2025-02-03 19:31 ` Alex Bennée
2025-02-04 1:51 ` Kim, Dongwon
2025-02-05 18:37 ` Dmitry Osipenko
2025-02-05 18:53 ` Kim, Dongwon
2025-02-05 20:08 ` Dmitry Osipenko
2025-02-05 22:13 ` Dmitry Osipenko
2025-02-12 2:46 ` Dmitry Osipenko
2025-02-14 6:03 ` Kasireddy, Vivek
2025-02-14 14:33 ` Alex Bennée
2025-02-14 16:03 ` Dmitry Osipenko
2025-02-17 15:22 ` Alex Bennée
2025-02-17 18:02 ` Dmitry Osipenko
2025-02-17 18:35 ` Alex Bennée
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='CAAfnVBmrCSk-TBMD7NnVkHtHf9mECMtmxg=ExZF5WZs1mtmqPg@mail.gmail.com' \
--to=gurchetansingh@chromium.org \
--cc=Jiqian.Chen@amd.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gert.wollny@collabora.com \
--cc=hi@alyssa.is \
--cc=honglei1.huang@amd.com \
--cc=julia.zhang@amd.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=roger.pau@citrix.com \
--cc=slp@redhat.com \
--cc=stefano.stabellini@amd.com \
--cc=xenia.ragiadakou@amd.com \
--cc=zzyiwei@chromium.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).