On Wed, Jan 22, 2020 at 04:16:35PM +0900, David Stevens wrote:
> Signed-off-by: David Stevens <steve...@chromium.org>
> ---
> virtio-gpu.tex | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/virtio-gpu.tex b/virtio-gpu.tex
> index af4ca61..a1f0210 100644
> --- a/virtio-gpu.tex
> +++ b/virtio-gpu.tex
> @@ -186,12 +186,16 @@ \subsubsection{Device Operation: Request
> header}\label{sec:Device Types / GPU De
> VIRTIO_GPU_CMD_UPDATE_CURSOR = 0x0300,
> VIRTIO_GPU_CMD_MOVE_CURSOR,
>
> + /* misc commands */
> + VIRTIO_GPU_CMD_RESOURCE_ASSIGN_UUID = 0x0400,
> +
> /* success responses */
> VIRTIO_GPU_RESP_OK_NODATA = 0x1100,
> VIRTIO_GPU_RESP_OK_DISPLAY_INFO,
> VIRTIO_GPU_RESP_OK_CAPSET_INFO,
> VIRTIO_GPU_RESP_OK_CAPSET,
> VIRTIO_GPU_RESP_OK_EDID,
> + VIRTIO_GPU_RESP_OK_RESOURCE_ASSIGN_UUID,
>
> /* error responses */
> VIRTIO_GPU_RESP_ERR_UNSPEC = 0x1200,
> @@ -454,6 +458,32 @@ \subsubsection{Device Operation:
> controlq}\label{sec:Device Types / GPU Device /
> This detaches any backing pages from a resource, to be used in case of
> guest swapping or object destruction.
>
> +\item[VIRTIO_GPU_CMD_RESOURCE_ASSIGN_UUID] Creates an exported object from
> + a resource. Request data is \field{struct
> + virtio_gpu_resource_assign_uuid}. Response type is
> + VIRTIO_GPU_RESP_OK_RESOURCE_ASSIGN_UUID, response data is \field{struct
> + virtio_gpu_resp_resource_assign_uuid}.
> +
> +\begin{lstlisting}
> +struct virtio_gpu_resource_assign_uuid {
> + struct virtio_gpu_ctrl_hdr hdr;
> + le32 resource_id;
> + le32 padding;
> +};
> +
> +struct virtio_gpu_resp_resource_assign_uuid {
> + struct virtio_gpu_ctrl_hdr hdr;
> + le64 uuid_low;
> + le64 uuid_high;
> +};
> +\end{lstlisting}
> +
ok but how is this then used? will there be more commands to pass
this uuid to another device?
> +The response contains a uuid which identifies the exported object created
> from
> +the host private resource.
Are the uuids as specified in rfc-4122? I guess we need to link to that spec
then
..
> Note that if the resource has an attached backing,
> +modifications made to the host private resource through the exported object
> by
> +other devices are not visible in the attached backing until they are
> transferred
> +into the backing.
> +
s/host/device/?
> \end{description}
>
> \subsubsection{Device Operation: cursorq}\label{sec:Device Types /
> GPU Device / Device Operation / Device Operation: cursorq}
> --
> 2.25.0.341.g760bfbb309-goog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
