[Intel-gfx] [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation

Zhang, Tina tina.zhang at intel.com
Fri Sep 29 07:49:58 UTC 2017



> -----Original Message-----
> From: Gerd Hoffmann [mailto:kraxel at redhat.com]
> Sent: Friday, September 29, 2017 3:29 PM
> To: Zhang, Tina <tina.zhang at intel.com>; zhenyuw at linux.intel.com; Wang, Zhi
> A <zhi.a.wang at intel.com>; Tian, Kevin <kevin.tian at intel.com>; Alex
> Williamson <alex.williamson at redhat.com>
> Cc: Daniel Vetter <daniel.vetter at ffwll.ch>; intel-gfx at lists.freedesktop.org;
> intel-gvt-dev at lists.freedesktop.org; Lv, Zhiyuan <zhiyuan.lv at intel.com>
> Subject: Re: [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation
> 
> On Fri, 2017-09-29 at 07:04 +0000, Zhang, Tina wrote:
> > So, there won't be dmabuf leaking problem, as we release all the
> > dmabuf_obj in the release ops when user space crashing.
> >
> > Can we just stop considering the way to fix the dmabuf life-cycle
> > issue and try to just consider the generic way to handle buffer
> > exposing?
> 
> Can you describe in more detail what you have in mind?
> 
> > Does the generic way need the close ioctl?
> 
> I think we don't need a close ioctl anyway.
Can you share your thoughts?
Do you think the fd interface is enough for all kinds of buffer exposed by Mdev?
Thanks.

BR,
Tina

> 
> cheers,
>   Gerd
> 



More information about the Intel-gfx mailing list