[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac03cba7-2f66-c4e3-c3e4-82f77483330d@nvidia.com>
Date: Fri, 14 Jul 2017 15:45:53 +0530
From: Kirti Wankhede <kwankhede@...dia.com>
To: Gerd Hoffmann <kraxel@...hat.com>,
"Zhang, Tina" <tina.zhang@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"zhenyuw@...ux.intel.com" <zhenyuw@...ux.intel.com>,
"chris@...is-wilson.co.uk" <chris@...is-wilson.co.uk>,
"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: [PATCH v10] vfio: ABI for mdev display dma-buf operation
On 7/14/2017 3:31 PM, Gerd Hoffmann wrote:
> Hi,
>
>> In case when VFIO region is used to provide surface to QEMU, plane_id
>> would be region index,
>
> Then we should name it "region_index" not "plane_id".
>
>> for example region 10 could be used for primary
>> surface and region 11 could be used for cursor surface. So in that
>> case,
>> mdev vendor driver should return plane_type and its corresponding
>> plane_id.
>
> Hmm? plane_type is the input (userspace -> kernel) parameter.
>
Yes, that's right. Sorry for confusion. And mdev vendor driver would
return which region to read.
Thanks,
Kirti
> cheers,
> Gerd
>
Powered by blists - more mailing lists