Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Gurchetan Singh <gurchetansingh@chromium.org>,
	Rob Clark <robdclark@gmail.com>, Huang Rui <ray.huang@amd.com>,
	Sergio Lopez <slp@redhat.com>,
	Akihiko Odaki <akihiko.odaki@daynix.com>,
	virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] [PATCH v1 2/2] virtio-gpu: Document VIRTIO_GPU_CAPSET_DRM
Date: Mon,  6 Nov 2023 00:17:28 +0300	[thread overview]
Message-ID: <20231105211728.808219-2-dmitry.osipenko@collabora.com> (raw)
In-Reply-To: <20231105211728.808219-1-dmitry.osipenko@collabora.com>

Document VIRTIO_GPU_CAPSET_DRM that is capset for the DRM native context
protocols which implement Linux DRM UAPIs over VirtIO-GPU, effectively
exposing host GPU to a Linux guest like it's a native/baremetal GPU.

Link: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14900
Link: https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/693
Link: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21658
Link: https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1274
Link: https://gitlab.freedesktop.org/digetx/mesa/-/commits/native-context-iris
Link: https://chromium.googlesource.com/chromiumos/platform/crosvm/+/69ecfb0e3913a4cd9048056f9a37cc496c7b9235
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
---
 device-types/gpu/description.tex | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/device-types/gpu/description.tex b/device-types/gpu/description.tex
index 4b8dd7733c31..29c8a97c3a3f 100644
--- a/device-types/gpu/description.tex
+++ b/device-types/gpu/description.tex
@@ -536,6 +536,8 @@ \subsubsection{Device Operation: controlq}\label{sec:Device Types / GPU Device /
 	Mesa's (mostly) autogenerated Vulkan protocol.
   \item \href{https://chromium.googlesource.com/chromiumos/platform/crosvm/+/refs/heads/main/rutabaga_gfx/src/cross_domain/cross_domain_protocol.rs}{VIRTIO_GPU_CAPSET_CROSS_DOMAIN} --
 	protocol for display virtualization via Wayland proxying.
+  \item \href{https://gitlab.freedesktop.org/virgl/virglrenderer/-/tree/master/src/drm}{VIRTIO_GPU_CAPSET_DRM} --
+	DRM native context protocols.
   \end{itemize*}
 
 \begin{lstlisting}
@@ -550,6 +552,7 @@ \subsubsection{Device Operation: controlq}\label{sec:Device Types / GPU Device /
 #define VIRTIO_GPU_CAPSET_GFXSTREAM_VULKAN 3
 #define VIRTIO_GPU_CAPSET_VENUS 4
 #define VIRTIO_GPU_CAPSET_CROSS_DOMAIN 5
+#define VIRTIO_GPU_CAPSET_DRM 6
 struct virtio_gpu_resp_capset_info {
         struct virtio_gpu_ctrl_hdr hdr;
         le32 capset_id;
-- 
2.41.0


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2023-11-05 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 21:17 [virtio-comment] [PATCH v1 1/2] virtio-gpu: Rename GFXSTREAM context capset to GFXSTREAM_VULKAN Dmitry Osipenko
2023-11-05 21:17 ` Dmitry Osipenko [this message]
2023-11-06  7:21 ` [virtio-comment] " 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=20231105211728.808219-2-dmitry.osipenko@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=gurchetansingh@chromium.org \
    --cc=kraxel@redhat.com \
    --cc=ray.huang@amd.com \
    --cc=robdclark@gmail.com \
    --cc=slp@redhat.com \
    --cc=virtio-comment@lists.oasis-open.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