[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1495184222.627.46.camel@redhat.com>
Date: Fri, 19 May 2017 10:57:02 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: "Chen, Xiaoguang" <xiaoguang.chen@...el.com>
Cc: Alex Williamson <alex.williamson@...hat.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"zhenyuw@...ux.intel.com" <zhenyuw@...ux.intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@...el.com>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>,
"Wang, Zhi A" <zhi.a.wang@...el.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 this. Have one ioctl where we pass in the plane id, get back a
plane description struct, and another where we pass in the plane
description struct and get back a dma-buf fd.
cheers,
Gerd
Powered by blists - more mailing lists