On Mon, Dec 11, 2023 at 10:48 PM Stefan Hajnoczi <stefa...@gmail.com> wrote:
> On Thu, 7 Dec 2023 at 09:55, Albert Esteve <aest...@redhat.com> wrote: > > > > v1: https://www.mail-archive.com/qemu-devel@nongnu.org/msg1005257.html > > v1 -> v2: > > - Solved an unitialized uuid value on vhost-user source > > - Changed cleanup strategy, and traverse all objects in the > > table to remove them instead. > > Please update the vhost-user specification > (docs/interop/vhost-user.rst) so people implementing front-ends and > back-ends are aware that only the back-end that added a shared > resource can remove it. > > Acked-by: Stefan Hajnoczi <stefa...@redhat.com> > > Will do :) Should I add the `Acked-by` manually to the commits or does it get automatically picked up later? BR, Albert PS: Happy New Year! > > > > Various improvements for the virtio-dmabuf module. > > This patch includes: > > > > - Check for ownership before allowing a vhost device > > to remove an object from the table. > > - Properly cleanup shared resources if a vhost device > > object gets cleaned up. > > - Rename virtio dmabuf functions to `virtio_dmabuf_*` > > > > Albert Esteve (3): > > hw/virtio: check owner for removing objects > > hw/virtio: cleanup shared resources > > hw/virtio: rename virtio dmabuf API > > > > hw/display/virtio-dmabuf.c | 36 ++++++++++++--- > > hw/virtio/vhost-user.c | 31 ++++++++++--- > > hw/virtio/vhost.c | 3 ++ > > include/hw/virtio/virtio-dmabuf.h | 43 ++++++++++------- > > tests/unit/test-virtio-dmabuf.c | 77 ++++++++++++++++++++++--------- > > 5 files changed, 138 insertions(+), 52 deletions(-) > > > > -- > > 2.43.0 > > > >
