search for: virtgpu_cmd_resource_flush

...ifndef VIRTGPU_HW_H +#define VIRTGPU_HW_H + +enum virtgpu_ctrl_type { + VIRTGPU_UNDEFINED = 0, + + /* 2d commands */ + VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100, + VIRTGPU_CMD_RESOURCE_CREATE_2D, + VIRTGPU_CMD_RESOURCE_UNREF, + VIRTGPU_CMD_SET_SCANOUT, + VIRTGPU_CMD_RESOURCE_FLUSH, + VIRTGPU_CMD_TRANSFER_TO_HOST_2D, + VIRTGPU_CMD_RESOURCE_ATTACH_BACKING, + VIRTGPU_CMD_RESOURCE_INVAL_BACKING, + + /* cursor commands */ + VIRTGPU_CMD_UPDATE_CURSOR = 0x0300, + VIRTGPU_CMD_MOVE_CURSOR, + + /* success responses */ + VIRTGPU_R...

Hi folks, Lets kick off the virtio-gpu review process, starting with the virtio protocol. This is a tiny patch series for qemu. Patch #1 carries the header file describing the virtual hardware: config space, command structs being sent over the rings, defines etc. Patch #2 adds a text file describing virtio-gpu to docs/specs/. It covers 2D support only for now. For anybody who wants to dig a

Hi folks, Lets kick off the virtio-gpu review process, starting with the virtio protocol. This is a tiny patch series for qemu. Patch #1 carries the header file describing the virtual hardware: config space, command structs being sent over the rings, defines etc. Patch #2 adds a text file describing virtio-gpu to docs/specs/. It covers 2D support only for now. For anybody who wants to dig a

...al guest user would create a 2D resource using +VIRTGPU_CMD_RESOURCE_CREATE_2D, attach backing store using +VIRTGPU_CMD_RESOURCE_ATTACH_BACKING, then attach the resource to a +scanout using VIRTGPU_CMD_SET_SCANOUT, then use +VIRTGPU_CMD_TRANSFER_SEND_2D to send updates to the resource, and +finally VIRTGPU_CMD_RESOURCE_FLUSH to flush the scanout buffers to +screen. + + +control queue commands (2D) +--------------------------- + +VIRTGPU_CMD_GET_DISPLAY_INFO: + Command: none (just struct virtgpu_ctrl_hdr). + Returns: struct virtgpu_resp_display_info. + + Retrieve the current output configuration. + +VIRTGPU_CMD_RESOU...

...t. What if x, y, width, and height are out-of-range for the given resource? What if width and height exceed the scanout width and height? Is it possible to unset the scanout for a resource? Can a resource be set on multiple scanouts? Does VIRTGPU_CMD_SET_SCANOUT need to be called between every VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? > +VIRTGPU_CMD_RESOURCE_ATTACH_BACKING: > + Command: struct virtgpu_resource_attach_backing > + > + Assign backing pages to a resource. > + > + This assign an array of guest pages (struct virtgpu_mem_entry) as "assigns" > + th...

...t. What if x, y, width, and height are out-of-range for the given resource? What if width and height exceed the scanout width and height? Is it possible to unset the scanout for a resource? Can a resource be set on multiple scanouts? Does VIRTGPU_CMD_SET_SCANOUT need to be called between every VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? > +VIRTGPU_CMD_RESOURCE_ATTACH_BACKING: > + Command: struct virtgpu_resource_attach_backing > + > + Assign backing pages to a resource. > + > + This assign an array of guest pages (struct virtgpu_mem_entry) as "assigns" > + th...

...th and height? Using only a subrectangle of the resource for the scanout is legal. > Is it possible to unset the scanout for a resource? Yes, use resource_id 0. > Can a resource be > set on multiple scanouts? Yes. > Does VIRTGPU_CMD_SET_SCANOUT need to be called between every > VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? Assignment is persistent. > > + the backing store for a resource. These pages are then used for the > > + transfer operations for that resource from that point on. > > + > > +VIRTGPU_CMD_RESOURCE_INVAL_BACKING: > > + Command: str...