Re: [virtio-comment] Re: [PATCH 1/2] virtio-gpu: add resource create blob

[Chia-I Wu <olvaffe@gmail.com>]

On Wed, Aug 19, 2020 at 12:00 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
>   Hi,
>
> > +For VIRTIO_GPU_BLOB_MEM_HOST3D and VIRTIO_GPU_BLOB_MEM_HOST3D_GUEST, the
> > +virtio-gpu resource MUST be created from the rendering context local object
> > +identified by the \field{blob_id}. The actual allocation is done via
> > +VIRTIO_GPU_CMD_SUBMIT_3D.
>
> Speaking of VIRTIO_GPU_CMD_SUBMIT_3D:  IIRC I saw the suggestion to
> separate out the submit_3d protocol headers somewhere (don't remember
> where, so I'm kind of replying here).  I think this is a very good idea
> to move them to a separate git repo / project, then have everyone use
> that.  The project will be a natural place for the protocol spec and we
> also can add a reference to it to the virtio specs.
Yes!  I think that is a prerequisite to spec the 3D mode.  Not just
the protocol header (virgl_protocol.h), but also virgl_hw.h that can
be referenced by VIRTIO_GPU_CMD_RESOURCE_CREATE_3D and
VIRTIO_GPU_CMD_GET_CAPSET.

>
> take care,
>   Gerd
>
>
> 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/
>