From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753010AbdESJPD (ORCPT ); Fri, 19 May 2017 05:15:03 -0400 Received: from mga05.intel.com ([192.55.52.43]:16791 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818AbdESJPC (ORCPT ); Fri, 19 May 2017 05:15:02 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,363,1491289200"; d="scan'208";a="970652235" From: "Chen, Xiaoguang" To: Gerd Hoffmann CC: "Tian, Kevin" , "linux-kernel@vger.kernel.org" , "zhenyuw@linux.intel.com" , Alex Williamson , "Lv, Zhiyuan" , "intel-gvt-dev@lists.freedesktop.org" , "Wang, Zhi A" Subject: RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Thread-Topic: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Thread-Index: AQHSwAN47y043l0J90m8wsAsHWts2aHgTQ8AgAGNjMCAAazCQIAAU9qAgAD30YCAAIqCgIAJhcZQ///LVYCAACZvAIABMD1g//+Lz4CAAGhigIAAfLgAgARXT/CAAHIJgIABcqeQgAH05ICAAMZxEIAAWgmAgAEfcYCAAIcF0P//h5IAABExSoA= Date: Fri, 19 May 2017 09:14:58 +0000 Message-ID: References: <1493372130-27727-1-git-send-email-xiaoguang.chen@intel.com> <20170504100833.199bc8ba@t450s.home> <1493967331.371.53.camel@redhat.com> <20170505091115.7a680636@t450s.home> <1494509273.17970.12.camel@redhat.com> <20170511094526.164985ee@w520.home> <20170511205829.672854c3@t450s.home> <1494580325.14352.57.camel@redhat.com> <20170512103828.4a1378a1@t450s.home> <20170515114409.414d1fdb@w520.home> <20170517154331.1b465f69@w520.home> <20170518085601.51e3296a@w520.home> <1495181089.627.33.camel@redhat.com> <1495184222.627.46.camel@redhat.com> In-Reply-To: <1495184222.627.46.camel@redhat.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v4J9F7bj000797 Hi Gerd, >-----Original Message----- >From: intel-gvt-dev [mailto:intel-gvt-dev-bounces@lists.freedesktop.org] On >Behalf Of Gerd Hoffmann >Sent: Friday, May 19, 2017 4:57 PM >To: Chen, Xiaoguang >Cc: Tian, Kevin ; linux-kernel@vger.kernel.org; >zhenyuw@linux.intel.com; Alex Williamson ; Lv, >Zhiyuan ; intel-gvt-dev@lists.freedesktop.org; Wang, Zhi >A >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. 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 plane. > >cheers, > Gerd > >_______________________________________________ >intel-gvt-dev mailing list >intel-gvt-dev@lists.freedesktop.org >https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev