Displaying 6 results from an estimated 6 matches for "virtgpu_cmd_resource_attach_backing".
2014 Sep 11
0
[PATCH 1/2] virtio-gpu/2d: add hardware spec include file
...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_RESP_OK_NODATA = 0x1100,
+ VIRTGPU_RESP_OK_DISPLAY_INFO,
+
+ /* error respo...
2014 Sep 11
9
[PATCH 0/2] virtio-gpu: hardware specification
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
2014 Sep 11
9
[PATCH 0/2] virtio-gpu: hardware specification
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
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...idth,
+height and format along with an identifier. The guest must then attach
+backing store to the resources in order for DMA transfers to
+work. This is like a GART in a real GPU.
+
+A typical 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_CM...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...source?
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"
> + the backing store for a resource. These pages are then used for the
> + tran...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...source?
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"
> + the backing store for a resource. These pages are then used for the
> + tran...