Displaying 9 results from an estimated 9 matches for "virtgpu_resource_inval_back".
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...s 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
> + transfer operations for that resource from that point on.
> +
> +VIRTGPU_CMD_RESOURCE_INVAL_BACKING:
> + Command: struct virtgpu_resource_inval_backing
Why is it called INVAL_BACKING instead of DETACH_BACKING? "Detach" is
logical since there is also an "attach" command.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...s 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
> + transfer operations for that resource from that point on.
> +
> +VIRTGPU_CMD_RESOURCE_INVAL_BACKING:
> + Command: struct virtgpu_resource_inval_backing
Why is it called INVAL_BACKING instead of DETACH_BACKING? "Detach" is
logical since there is also an "attach" command.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not...
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 12
1
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...the host driver will store them in VRAM or main memory. Quite
how to fail gracefully is a question, probably need to report to the
guest what context did the allocation and see if we can destroy it.
>> > +
>> > +VIRTGPU_CMD_RESOURCE_INVAL_BACKING:
>> > + Command: struct virtgpu_resource_inval_backing
>>
>> Why is it called INVAL_BACKING instead of DETACH_BACKING? "Detach" is
>> logical since there is also an "attach" command.
>
> No particular reason I think. Dave?
>
Not reason I can remember, I think I was thinking of having separate
inval a...
2014 Sep 12
1
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...the host driver will store them in VRAM or main memory. Quite
how to fail gracefully is a question, probably need to report to the
guest what context did the allocation and see if we can destroy it.
>> > +
>> > +VIRTGPU_CMD_RESOURCE_INVAL_BACKING:
>> > + Command: struct virtgpu_resource_inval_backing
>>
>> Why is it called INVAL_BACKING instead of DETACH_BACKING? "Detach" is
>> logical since there is also an "attach" command.
>
> No particular reason I think. Dave?
>
Not reason I can remember, I think I was thinking of having separate
inval a...
2014 Sep 11
0
[PATCH 1/2] virtio-gpu/2d: add hardware spec include file
...ddr;
+ uint32_t length;
+ uint32_t pad;
+};
+
+/* VIRTGPU_CMD_RESOURCE_ATTACH_BACKING */
+struct virtgpu_resource_attach_backing {
+ struct virtgpu_ctrl_hdr hdr;
+ uint32_t resource_id;
+ uint32_t nr_entries;
+};
+
+/* VIRTGPU_CMD_RESOURCE_INVAL_BACKING */
+struct virtgpu_resource_inval_backing {
+ struct virtgpu_ctrl_hdr hdr;
+ uint32_t resource_id;
+};
+
+/* VIRTGPU_RESP_OK_DISPLAY_INFO */
+#define VIRTGPU_MAX_SCANOUTS 16
+struct virtgpu_resp_display_info {
+ struct virtgpu_ctrl_hdr hdr;
+ struct virtgpu_display_one {
+ uint32_t enabled;
+...
2014 Sep 12
0
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...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: struct virtgpu_resource_inval_backing
>
> Why is it called INVAL_BACKING instead of DETACH_BACKING? "Detach" is
> logical since there is also an "attach" command.
No particular reason I think. Dave?
cheers,
Gerd
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...+ Assign backing pages to a resource.
+
+ This assign an array of guest pages (struct virtgpu_mem_entry) as
+ 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: struct virtgpu_resource_inval_backing
+
+ Detach backing pages from a resource.
+
+ This detaches any backing pages from a resource, to be used in case of
+ guest swapping or object destruction.
+
+
+cursor queue commands
+---------------------
+
+VIRTGPU_CMD_UPDATE_CURSOR
+ Command: struct virtgpu_update_cursor
+
+ Update curs...