From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] virtio-gpu: add 3d command overview
Date: Mon, 2 Dec 2019 11:58:51 -0500 [thread overview]
Message-ID: <20191202115816-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191129083130.15353-1-kraxel@redhat.com>
On Fri, Nov 29, 2019 at 09:31:30AM +0100, Gerd Hoffmann wrote:
> Add 3d commands to the command enumeration.
> Add a section with a very short overview.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Pls don't forget to create github issues and request
voting when you are ready.
> ---
> virtio-gpu.tex | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/virtio-gpu.tex b/virtio-gpu.tex
> index eced3095a494..631aaf24ea18 100644
> --- a/virtio-gpu.tex
> +++ b/virtio-gpu.tex
> @@ -213,6 +213,16 @@ \subsubsection{Device Operation: Request header}\label{sec:Device Types / GPU De
> VIRTIO_GPU_CMD_GET_EDID,
> VIRTIO_GPU_CMD_RESOURCE_CREATE_2D_SHARED,
>
> + /* 3d commands (OpenGL) */
> + VIRTIO_GPU_CMD_CTX_CREATE = 0x0200,
> + VIRTIO_GPU_CMD_CTX_DESTROY,
> + VIRTIO_GPU_CMD_CTX_ATTACH_RESOURCE,
> + VIRTIO_GPU_CMD_CTX_DETACH_RESOURCE,
> + VIRTIO_GPU_CMD_RESOURCE_CREATE_3D,
> + VIRTIO_GPU_CMD_TRANSFER_TO_HOST_3D,
> + VIRTIO_GPU_CMD_TRANSFER_FROM_HOST_3D,
> + VIRTIO_GPU_CMD_SUBMIT_3D,
> +
> /* cursor commands */
> VIRTIO_GPU_CMD_UPDATE_CURSOR = 0x0300,
> VIRTIO_GPU_CMD_MOVE_CURSOR,
> @@ -488,6 +498,31 @@ \subsubsection{Device Operation: controlq}\label{sec:Device Types / GPU Device /
>
> \end{description}
>
> +\subsubsection{Device Operation: controlq (3d)}\label{sec:Device Types / GPU Device / Device Operation / Device Operation: controlq (3d)}
> +
> +These commands are supported by the device if the VIRTIO_GPU_F_VIRGL
> +feature flag is set.
> +
> +\begin{description}
> +
> +\item[VIRTIO_GPU_CMD_CTX_CREATE]
> +\item[VIRTIO_GPU_CMD_CTX_DESTROY]
> +\item[VIRTIO_GPU_CMD_CTX_ATTACH_RESOURCE]
> +\item[VIRTIO_GPU_CMD_CTX_DETACH_RESOURCE]
> + Manage OpenGL contexts.
> +
> +\item[VIRTIO_GPU_CMD_RESOURCE_CREATE_3D]
> + Create OpenGL resources.
> +
> +\item[VIRTIO_GPU_CMD_TRANSFER_TO_HOST_3D]
> +\item[VIRTIO_GPU_CMD_TRANSFER_FROM_HOST_3D]
> + Transfer data from and to OpenGL resources.
> +
> +\item[VIRTIO_GPU_CMD_SUBMIT_3D]
> + Submit rendering commands (mesa gallium command stream).
> +
> +\end{description}
> +
> \subsubsection{Device Operation: cursorq}\label{sec:Device Types / GPU Device / Device Operation / Device Operation: cursorq}
>
> Both cursorq commands use the same command struct.
> --
> 2.18.1
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2019-12-02 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 8:31 [virtio-dev] [PATCH] virtio-gpu: add 3d command overview Gerd Hoffmann
2019-11-29 14:11 ` Matti Moell
2019-12-02 16:58 ` Michael S. Tsirkin [this message]
2019-12-03 9:37 ` Gerd Hoffmann
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=20191202115816-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=virtio-dev@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