Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753843AbdGNKQE (ORCPT ); Fri, 14 Jul 2017 06:16:04 -0400 Received: from hqemgate14.nvidia.com ([216.228.121.143]:7310 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753472AbdGNKQD (ORCPT ); Fri, 14 Jul 2017 06:16:03 -0400 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Fri, 14 Jul 2017 03:16:02 -0700 Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation To: Gerd Hoffmann , "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" 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> <1500026519.28252.7.camel@redhat.com> X-Nvconfidentiality: public From: Kirti Wankhede Message-ID: Date: Fri, 14 Jul 2017 15:45:53 +0530 MIME-Version: 1.0 In-Reply-To: <1500026519.28252.7.camel@redhat.com> X-Originating-IP: [10.24.70.138] X-ClientProxiedBy: DRBGMAIL104.nvidia.com (10.18.16.23) To bgmail102.nvidia.com (10.25.59.11) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 637 Lines: 28 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 >