On Mon, Feb 19, 2024 at 11:45 AM Albert Esteve wrote:
>
>
>
> On Thu, Feb 15, 2024 at 10:45 AM Albert Esteve wrote:
>
>>
>>
>> On Tue, Feb 6, 2024 at 12:11 AM Alex Bennée
>> wrote:
>>
>>> Albert Esteve writes:
>>>
>>> > Ensure that we cleanup all virtio shared
>>> > resources when the vhost
On Thu, Feb 15, 2024 at 10:45 AM Albert Esteve wrote:
>
>
> On Tue, Feb 6, 2024 at 12:11 AM Alex Bennée
> wrote:
>
>> Albert Esteve writes:
>>
>> > Ensure that we cleanup all virtio shared
>> > resources when the vhost devices is cleaned
>> > up (after a hot unplug, or a crash).
>> >
>> > To
Albert Esteve writes:
> On Tue, Feb 6, 2024 at 12:11 AM Alex Bennée wrote:
>
> Albert Esteve writes:
>
> > Ensure that we cleanup all virtio shared
> > resources when the vhost devices is cleaned
> > up (after a hot unplug, or a crash).
> >
> > To do so, we add a new function to the
On Tue, Feb 6, 2024 at 12:11 AM Alex Bennée wrote:
> Albert Esteve writes:
>
> > Ensure that we cleanup all virtio shared
> > resources when the vhost devices is cleaned
> > up (after a hot unplug, or a crash).
> >
> > To do so, we add a new function to the virtio_dmabuf
> > API called
Albert Esteve writes:
> Ensure that we cleanup all virtio shared
> resources when the vhost devices is cleaned
> up (after a hot unplug, or a crash).
>
> To do so, we add a new function to the virtio_dmabuf
> API called `virtio_dmabuf_vhost_cleanup`, which
> loop through the table and removes
Ensure that we cleanup all virtio shared
resources when the vhost devices is cleaned
up (after a hot unplug, or a crash).
To do so, we add a new function to the virtio_dmabuf
API called `virtio_dmabuf_vhost_cleanup`, which
loop through the table and removes all
resources owned by the vhost device
