On Tue, 30 Jan 2024 at 15:10, Marc-André Lureau
wrote:
>
> Hi
>
> On Tue, Jan 30, 2024 at 5:01 PM Manos Pitsidianakis
> wrote:
> >
> > On Tue, 30 Jan 2024 at 14:50, Marc-André Lureau
> > wrote:
> > >
> > > Hi
> > >
> > > On Mon, Jan 29, 2024 at 7:46 PM Manos Pitsidianakis
> > > wrote:
> > > >
Hi
On Tue, Jan 30, 2024 at 5:01 PM Manos Pitsidianakis
wrote:
>
> On Tue, 30 Jan 2024 at 14:50, Marc-André Lureau
> wrote:
> >
> > Hi
> >
> > On Mon, Jan 29, 2024 at 7:46 PM Manos Pitsidianakis
> > wrote:
> > >
> > > When the Rutabaga GPU device frees resources, it calls
> > >
On Tue, 30 Jan 2024 at 14:50, Marc-André Lureau
wrote:
>
> Hi
>
> On Mon, Jan 29, 2024 at 7:46 PM Manos Pitsidianakis
> wrote:
> >
> > When the Rutabaga GPU device frees resources, it calls
> > rutabaga_resource_unref for that resource_id. However, when the generic
> > VirtIOGPU functions
Hi
On Mon, Jan 29, 2024 at 7:46 PM Manos Pitsidianakis
wrote:
>
> When the Rutabaga GPU device frees resources, it calls
> rutabaga_resource_unref for that resource_id. However, when the generic
> VirtIOGPU functions destroys resources, it only removes the
> virtio_gpu_simple_resource from the
On Tue, 30 Jan 2024 03:26, Gurchetan Singh wrote:
On Mon, Jan 29, 2024 at 7:46 AM Manos Pitsidianakis <
manos.pitsidiana...@linaro.org> wrote:
When the Rutabaga GPU device frees resources, it calls
rutabaga_resource_unref for that resource_id. However, when the generic
VirtIOGPU functions
On Mon, Jan 29, 2024 at 7:46 AM Manos Pitsidianakis <
manos.pitsidiana...@linaro.org> wrote:
> When the Rutabaga GPU device frees resources, it calls
> rutabaga_resource_unref for that resource_id. However, when the generic
> VirtIOGPU functions destroys resources, it only removes the
>
When the Rutabaga GPU device frees resources, it calls
rutabaga_resource_unref for that resource_id. However, when the generic
VirtIOGPU functions destroys resources, it only removes the
virtio_gpu_simple_resource from the device's VirtIOGPU->reslist list.
The rutabaga resource associated with