From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Dmitry Osipenko" <dmitry.osipenko@collabora.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>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gert Wollny" <gert.wollny@collabora.com>,
qemu-devel@nongnu.org,
"Gurchetan Singh" <gurchetansingh@chromium.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 v5 8/8] docs/system: Expand the virtio-gpu documentation
Date: Tue, 21 Jan 2025 13:26:55 +0900 [thread overview]
Message-ID: <171b1cd3-1077-438c-a27c-3b9b3ce25f0f@daynix.com> (raw)
In-Reply-To: <87ikq9r7wj.fsf@draig.linaro.org>
On 2025/01/20 21:23, Alex Bennée wrote:
> Akihiko Odaki <akihiko.odaki@daynix.com> writes:
>
>> On 2025/01/20 7:00, Dmitry Osipenko 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: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>>> 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 | 94 ++++++++++++++++++++++++++++--
>>> 1 file changed, 88 insertions(+), 6 deletions(-)
>>> diff --git a/docs/system/devices/virtio-gpu.rst
>>> b/docs/system/devices/virtio-gpu.rst
>>> index f20c60016376..79af291a9316 100644
>>> --- a/docs/system/devices/virtio-gpu.rst
>>> +++ b/docs/system/devices/virtio-gpu.rst
>>> @@ -4,14 +4,96 @@
>>> virtio-gpu
>>> ==========
>>> -This document explains the setup and usage of the virtio-gpu
>>> device.
>>> -The virtio-gpu device paravirtualizes the GPU and display controller.
>>> -
>>> -Linux kernel support
>>> ---------------------
>>> +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.
>>> +
>>> +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.
>>> +
>>> +Host requirements
>>> +-----------------
>>> +
>>> +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.
>>> +
>>> +.. list-table:: Host Requirements
>>> + :header-rows: 1
>>> +
>>> + * - Mode
>>> + - Kernel
>>> + - Userspace
>>> + * - virtio-gpu
>>> + - framebuffer enabled
>>> + - GTK or SDL display
>>> + * - virtio-gpu-gl (OpenGL pass-through)
>>> + - GPU enabled
>>> + - libvirglrenderer (virgl support)
>>> + * - virtio-gpu-gl (rutabaga/gfxstream)
>>> + - GPU enabled
>>> + - aemu/rutabaga_gfx_ffi or vhost-user client with 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.13+
>>> + - libvirglrenderer (>= 1.0.0, DRM renderer support)
>>> + * - virtio-gpu-gl (vDRM native context/Intel i915)
>>> + - Linux 6.13+
>>> + - libvirglrenderer (`mr1384`_, DRM renderer support)
>>> +
>>> +.. _mr1384: https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1384
>>> +
>>> +Guest requirements
>>> +------------------
>>> virtio-gpu requires a guest Linux kernel built with the
>>> -``CONFIG_DRM_VIRTIO_GPU`` option.
>>> +``CONFIG_DRM_VIRTIO_GPU`` option. Otherwise for 3D accelerations you
>>> +will need support from Mesa configured for whichever encapsulation you
>>> +need.
>>> +
>>> +.. list-table:: Guest Requirements
>>> + :header-rows: 1
>>> +
>>> + * - Mode
>>> + - Mesa Version
>>> + - Mesa build flags
>>> + * - virtio-gpu
>>> + - n/a
>>> + - n/a
>>> + * - virtio-gpu-gl (OpenGL pass-through)
>>> + - 20.3.0+
>>> + - -Dgallium-drivers=virgl
>>> + * - virtio-gpu-gl (rutabaga/gfxstream)
>>> + - 24.3.0+
>>> + - -Dvulkan-drivers=gfxstream
>>> + * - virtio-gpu-gl (Vulkan pass-through)
>>> + - 24.2+
>>> + - -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
>>> +
>>> +.. _mr29870: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29870
>>
>> I feel the dependency information for virglrenderer and Mesa are more
>> suited for the Mesa documentation as they are not specific to QEMU and
>> potentially useful also for e.g., libkrun and crosvm.
>
> I think while everything is in so much flux it doesn't hurt to include
> in our docs. I don't know if mesa currently has a dedicated page for GPU
> virtualisation.
Mesa has pages for VirGL and Venus, which can be linked from the
respective parts of this documentation. gfxstream is not documented but
I think most people will use it only for Android anyway. A documentation
for DRM native context will be a nice addition for Mesa. I will not
object if you put this information to QEMU documentation though.
>
>
>>
>>> +
>>> +Further information
>>> +...................
>>
>> I'm not sure about putting the below sections behind "Further
>> information". Anyone who want to use this feature will need to know
>> the command line described below.
>>
>>> QEMU virtio-gpu variants
>>> ------------------------
>
next prev parent reply other threads:[~2025-01-21 4:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 22:00 [PATCH v5 0/8] Support virtio-gpu DRM native context Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 1/8] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 2/8] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 3/8] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 4/8] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
[not found] ` <87cyghr3l2.fsf@draig.linaro.org>
2025-01-22 12:18 ` Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 5/8] virtio-gpu: Support DRM native context Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 6/8] ui/sdl2: Don't disable scanout when display is refreshed Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 7/8] ui/gtk: " Dmitry Osipenko
2025-01-19 22:00 ` [PATCH v5 8/8] docs/system: Expand the virtio-gpu documentation Dmitry Osipenko
[not found] ` <c2e1c362-5d02-488e-b849-d0b14781a60f@daynix.com>
[not found] ` <87ikq9r7wj.fsf@draig.linaro.org>
2025-01-21 4:26 ` Akihiko Odaki [this message]
2025-01-26 18:06 ` Dmitry Osipenko
2025-01-27 4:57 ` Akihiko Odaki
2025-02-02 22:08 ` Dmitry Osipenko
2025-02-03 5:31 ` Akihiko Odaki
2025-02-05 17:40 ` Dmitry Osipenko
2025-02-06 5:41 ` Akihiko Odaki
2025-02-09 21:03 ` Dmitry Osipenko
2025-02-13 4:32 ` Akihiko Odaki
2025-02-18 6:27 ` Dmitry Osipenko
2025-02-18 6:35 ` Dmitry Osipenko
2025-02-27 6:40 ` Akihiko Odaki
[not found] ` <871pwxqyr3.fsf@draig.linaro.org>
2025-01-22 12:25 ` [PATCH v5 0/8] Support virtio-gpu DRM native context Dmitry Osipenko
2025-01-22 17:00 ` Alex Bennée
2025-01-23 11:23 ` Dmitry Osipenko
2025-01-23 11:58 ` Alex Bennée
2025-01-23 12:37 ` Dmitry Osipenko
2025-01-27 14:50 ` 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=171b1cd3-1077-438c-a27c-3b9b3ce25f0f@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=Jiqian.Chen@amd.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=gurchetansingh@chromium.org \
--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).