Hi Gerd,

>-----Original Message-----
>From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
>Behalf Of Gerd Hoffmann
>Sent: Friday, May 19, 2017 4:57 PM
>To: Chen, Xiaoguang <xiaoguang.c...@intel.com>
>Cc: Tian, Kevin <kevin.t...@intel.com>; linux-kernel@vger.kernel.org;
>zhen...@linux.intel.com; Alex Williamson <alex.william...@redhat.com>; Lv,
>Zhiyuan <zhiyuan...@intel.com>; intel-gvt-...@lists.freedesktop.org; Wang, Zhi
>A <zhi.a.w...@intel.com>
>Subject: Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf
>  Hi,
>> >We could also do it the other way around:  Instead of having the
>> >kernel returning
>> >the plane description userspace could pass it in, and the kernel
>> >throws -EINVAL in
>> >case it doesn't match due to things having changed meanwhile.
>> Or just return a dmabuf  based on the current plane ?
>If gvt is able to hand out dma-bufs for inactive planes, then yes, we can do 
>Have one ioctl where we pass in the plane id, get back a plane description 
>and another where we pass in the plane description struct and get back a dma-
>buf fd.
Or more simply just pass the plane id, because even the plane description did 
not match the current one we will eventually create a dmabuf based on current 

>  Gerd
>intel-gvt-dev mailing list

Reply via email to