search for: virtgpu_mem_entry

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

...VIRTGPU_CMD_TRANSFER_TO_HOST_2D: simple transfer to_host */ +struct virtgpu_transfer_to_host_2d { + struct virtgpu_ctrl_hdr hdr; + uint32_t resource_id; + uint32_t offset; + uint32_t width; + uint32_t height; + uint32_t x; + uint32_t y; +}; + +struct virtgpu_mem_entry { + uint64_t addr; + 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_INV...

...re 0,0 is in relation to the screen, and in which direction positive numbers move? I'm assuming 0,0 is top left, and larger x moves right, larger y moves down. Are there restrictions against rectangles that overlap beyond screen boundaries? > + This assign an array of guest pages (struct virtgpu_mem_entry) as s/assign/assigns/ -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 539 bytes Desc: OpenPGP digital si...

...re 0,0 is in relation to the screen, and in which direction positive numbers move? I'm assuming 0,0 is top left, and larger x moves right, larger y moves down. Are there restrictions against rectangles that overlap beyond screen boundaries? > + This assign an array of guest pages (struct virtgpu_mem_entry) as s/assign/assigns/ -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 539 bytes Desc: OpenPGP digital si...

...long with an destination offset into the + resource, and a box to transfer from the host backing for the + resource. + +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 + 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...

...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 > + 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_BAC...

...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 > + 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_BAC...