[Intel-gfx] [PATCH v10] vfio: ABI for mdev display dma-buf operation
Gerd Hoffmann
kraxel at redhat.com
Wed Jul 19 06:25:00 UTC 2017
On Wed, 2017-07-19 at 00:16 +0000, Zhang, Tina wrote:
> > -----Original Message-----
> > From: Gerd Hoffmann [mailto:kraxel at redhat.com]
> > Sent: Monday, July 17, 2017 7:03 PM
> > To: Kirti Wankhede <kwankhede at nvidia.com>; Zhang, Tina
> > <tina.zhang at intel.com>; Tian, Kevin <kevin.tian at intel.com>; linux-
> > kernel at vger.kernel.org; intel-gfx at lists.freedesktop.org;
> > alex.williamson at redhat.com; zhenyuw at linux.intel.com; chris at chris-
> > wilson.co.uk; Lv, Zhiyuan <zhiyuan.lv at intel.com>; intel-gvt-
> > dev at lists.freedesktop.org; Wang, Zhi A <zhi.a.wang at intel.com>
> > Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf
> > operation
> >
> > Hi,
> >
> > > No need of flag here. If vGPU driver is not loaded in the guest,
> > > there
> > > is no surface being managed by vGPU, in that case this size will
> > > be
> > > zero.
> >
> > Ok, we certainly have the same situation with intel. When the
> > guest driver is not
> > loaded (yet) there is no valid surface.
> >
> > We should cleanly define what the ioctl should do in that case, so
> > all drivers
> > behave the same way.
> >
> > I'd suggest that all fields defining the surface (drm_format,
> > width, height, stride,
> > size) should be set to zero in that case.
>
> Yeah, it's reasonable. How about the return value? Currently, the
> ioctl also returns "-ENODEV" in that situation.
I think it should not return an error. Querying the plane parameters
worked fine.
cheers,
Gerd
More information about the Intel-gfx
mailing list