From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation Date: Fri, 14 Jul 2017 12:01:59 +0200 Message-ID: <1500026519.28252.7.camel@redhat.com> References: <1499293795-6265-1-git-send-email-tina.zhang@intel.com> <980a5c09-fa8a-255d-19ad-acf4bb29d271@nvidia.com> <1499753648.8257.3.camel@redhat.com> <20170711091236.run4zirxmr34kazb@phenom.ffwll.local> <237F54289DF84E4997F34151298ABEBC7C57BF86@SHSMSX101.ccr.corp.intel.com> <20170712074038.izr6ureby4vwtq27@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Kirti Wankhede , "Zhang, Tina" , "Tian, Kevin" , "linux-kernel@vger.kernel.org" , "intel-gfx@lists.freedesktop.org" , "alex.williamson@redhat.com" , "zhenyuw@linux.intel.com" , "chris@chris-wilson.co.uk" , "Lv, Zhiyuan" , "intel-gvt-dev@lists.freedesktop.org" , "Wang, Zhi A" List-Id: intel-gfx@lists.freedesktop.org ICBIaSwKCj4gSW4gY2FzZSB3aGVuIFZGSU8gcmVnaW9uIGlzIHVzZWQgdG8gcHJvdmlkZSBzdXJm YWNlIHRvIFFFTVUsIHBsYW5lX2lkCj4gd291bGQgYmUgcmVnaW9uIGluZGV4LAoKVGhlbiB3ZSBz aG91bGQgbmFtZSBpdCAicmVnaW9uX2luZGV4IiBub3QgInBsYW5lX2lkIi4KCj4gZm9yIGV4YW1w bGUgcmVnaW9uIDEwIGNvdWxkIGJlIHVzZWQgZm9yIHByaW1hcnkKPiBzdXJmYWNlIGFuZCByZWdp b24gMTEgY291bGQgYmUgdXNlZCBmb3IgY3Vyc29yIHN1cmZhY2UuIFNvIGluIHRoYXQKPiBjYXNl LAo+IG1kZXYgdmVuZG9yIGRyaXZlciBzaG91bGQgcmV0dXJuIHBsYW5lX3R5cGUgYW5kIGl0cyBj b3JyZXNwb25kaW5nCj4gcGxhbmVfaWQuCgpIbW0/ICBwbGFuZV90eXBlIGlzIHRoZSBpbnB1dCAo dXNlcnNwYWNlIC0+IGtlcm5lbCkgcGFyYW1ldGVyLgoKY2hlZXJzLAogIEdlcmQKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkludGVsLWdmeCBtYWlsaW5n IGxpc3QKSW50ZWwtZ2Z4QGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpodHRwczovL2xpc3RzLmZyZWVk ZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ludGVsLWdmeAo= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753620AbdGNKCF (ORCPT ); Fri, 14 Jul 2017 06:02:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43016 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753302AbdGNKCE (ORCPT ); Fri, 14 Jul 2017 06:02:04 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 9490A369C4 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=kraxel@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 9490A369C4 Message-ID: <1500026519.28252.7.camel@redhat.com> Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation From: Gerd Hoffmann To: Kirti Wankhede , "Zhang, Tina" , "Tian, Kevin" , "linux-kernel@vger.kernel.org" , "intel-gfx@lists.freedesktop.org" , "alex.williamson@redhat.com" , "zhenyuw@linux.intel.com" , "chris@chris-wilson.co.uk" , "Lv, Zhiyuan" , "intel-gvt-dev@lists.freedesktop.org" , "Wang, Zhi A" Date: Fri, 14 Jul 2017 12:01:59 +0200 In-Reply-To: References: <1499293795-6265-1-git-send-email-tina.zhang@intel.com> <980a5c09-fa8a-255d-19ad-acf4bb29d271@nvidia.com> <1499753648.8257.3.camel@redhat.com> <20170711091236.run4zirxmr34kazb@phenom.ffwll.local> <237F54289DF84E4997F34151298ABEBC7C57BF86@SHSMSX101.ccr.corp.intel.com> <20170712074038.izr6ureby4vwtq27@phenom.ffwll.local> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 14 Jul 2017 10:02:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. cheers, Gerd