Profile

> +\begin(lstlisting) > +struct virtio_gpu_status_freezing ( > + struct virtio_gpu_ctrl_hdr hdr; > + __u32 freezing; > +); > +\end(lstlisting) > +This is added for S3 function in guest with virtio-gpu. When guest does > +S3, let it notify QEMU if virtio-gpu is in freezing status or not ...

Hi, > +\item[VIRTIO_GPU_CMD_STATUS_FREEZING] > +Notify freezing status through controlq. > +Request data is \field(struct virtio_gpu_status_freezing). > +Response type is VIRTIO_GPU_RESP_OK_NODATA. > + > +Guest notifies QEMU if virtio-gpu is in freezing status or not in \field(freezing). ...

On Wed, Sep 08, 2021 at 06:29:52PM -0700, Gurchetan Singh wrote: > Capability sets will be used as a proxy for the context type, > so add more detail regarding their use. > > Signed-off-by: Gurchetan Singh Reviewed-by: Gerd Hoffmann

On Wed, Sep 08, 2021 at 06:29:53PM -0700, Gurchetan Singh wrote: > This brings explicit context initialization and different types > to virtio-gpu. > > In the past, VIRTIO_GPU_F_VIRGL meant the virglrenderer support. > With VIRTIO_GPU_F_VIRGL + VIRTIO_GPU_F_CONTEXT_INIT, this means > generic ...

Hi, > struct virtio_gpu_ctrl_hdr ( > le32 type; > le32 flags; > le64 fence_id; > le32 ctx_id; > - le32 padding; > + le32 info; How about u8 ring_idx; u8 padding[3]; ? Otherwise this looks all sane to me. take care, Gerd