All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "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>,
	"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Cc: "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>,
	"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 v8 10/10] docs/system: virtio-gpu: Document host/guest requirements
Date: Fri, 14 Feb 2025 19:27:28 +0300	[thread overview]
Message-ID: <27c46923-53af-4185-afe2-0fd72fc7bb86@collabora.com> (raw)
In-Reply-To: <c3fe5de2-8e16-406b-9f27-c7ad88201222@daynix.com>

On 2/13/25 07:47, Akihiko Odaki wrote:
> On 2025/02/10 1:56, 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: 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 | 106 ++++++++++++++++++++++++++++-
>>   1 file changed, 104 insertions(+), 2 deletions(-)
>>
>> diff --git a/docs/system/devices/virtio-gpu.rst b/docs/system/devices/
>> virtio-gpu.rst
>> index ea3eb052df3c..664fc4000fa9 100644
>> --- a/docs/system/devices/virtio-gpu.rst
>> +++ b/docs/system/devices/virtio-gpu.rst
>> @@ -5,14 +5,34 @@ 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.
>> +
>> +virtio-gpu requirements
>> +-----------------------
>>     Linux kernel support
>> ---------------------
>> +^^^^^^^^^^^^^^^^^^^^
>>     virtio-gpu requires a guest Linux kernel built with the
>>   ``CONFIG_DRM_VIRTIO_GPU`` option.
>>   +Host Linux kernel requirements vary depending on a used virtio-gpu
>> +capabilities. See further sections for a detailed descriptions.
> 
> The section for 3D acceleration follows so let's defer the description
> for the host requirements to that section.
> 
> Perhaps the section title may be changed to clarify that it only
> describes the guest Linux kernel requirement to exclude the host Linux
> kernel requirement as well as guest Mesa.

Alright, think I now see what you meant in the comment to v7.

>> +.. list-table:: Linux Host Requirements
>> +  :header-rows: 1
>> +
>> +  * - Capability
>> +    - Kernel
>> +    - Rutabaga build flags
>> +  * - Vulkan+Wayland pass-through
>> +    - Linux 6.13+
>> +    - Follow `gfxstream-enabled rutabaga`_ build instructions
> 
> It is odd that the column header says "build flags", and this cell says
> "Follow `gfxstream-enabled rutabaga`_ build instructions".
> 
> I think you can simply remove this column. This section already says it
> leverages Rutabaga and the crosvm book provides build instructions.

In the other reply you said that you're strongly opposed to adding any
Mesa/virglrenderer build flags to the QEMU doc. I'm going to remove all
build flags in v9. Please let me know if I misunderstood you and you're
meaning something else.

-- 
Best regards,
Dmitry


      parent reply	other threads:[~2025-02-14 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 16:56 [PATCH v8 00/10] Support virtio-gpu DRM native context Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 01/10] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 02/10] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 03/10] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 04/10] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 05/10] virtio-gpu: Support DRM native context Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 06/10] ui/sdl2: Don't disable scanout when display is refreshed Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 07/10] ui/gtk: " Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 08/10] docs/system: virtio-gpu: Add link to Mesa VirGL doc Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 09/10] docs/system: virtio-gpu: Update Venus link Dmitry Osipenko
2025-02-09 16:56 ` [PATCH v8 10/10] docs/system: virtio-gpu: Document host/guest requirements Dmitry Osipenko
2025-02-13  4:47   ` Akihiko Odaki
2025-02-13 10:18     ` Alex Bennée
2025-02-13 10:30       ` Akihiko Odaki
2025-02-14 16:27     ` Dmitry Osipenko [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=27c46923-53af-4185-afe2-0fd72fc7bb86@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.