Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3669417ybl; Sun, 25 Aug 2019 21:38:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyt5ESk9zIbU7FLMjwD5VqM69OzfLm6DEKNWrpBWqTklGG4ZT1zTyUaKvFG9xcd9zDOIFYd X-Received: by 2002:a63:6205:: with SMTP id w5mr13432896pgb.199.1566794288532; Sun, 25 Aug 2019 21:38:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566794288; cv=none; d=google.com; s=arc-20160816; b=dP5ZTdMnbuDiohIGjL8aURzfz51hfQZfhJafp2QeAHbmugP18DbEuWUayCOh56s5vR 4BEoe3qrOfW1GWelHjohR9cTCKhr3iMeLINjZXKsSkr4l/mcPWTXBhZO4bRyJAF7+/Co cnJNztF+nqZ2qq1d0IRsAzvWcHO/9d6yv4x6ZUiXYLYP/f9w+2kCgSX7pZs8oDT9spjP ggxoEXwmPcZgl+lTZmpC2UXaRgKrGUYSRIzVu6Wp5ZB79OifDHhgQUiZFC0Abio4ii5w R7jIKYaDDy00UYww0DYxgWcOo9wfNU3V+d9H37WmJ2rL7oYLmvtjKMHyLHzwi8t1S3oQ Yq4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=T+6j3N2jQo1QQ6kp2CeHy+2/WKAX6wHB2sXvAG2BQVI=; b=uhYBZdrS3b8CvJxj15dDmEvf/ByI86GU/hTaDofuxcp5ba8LzSjwCvZ+dLW2tuqj9P +ZfoVR9tlwP4WkqD7luG3ruzy8rM4qbex61FOT4Y9adYlfOtwzxrQLkBOYrGU3LYbKoq KjbRKzX4hpJXcOlEe9/3gTd17+XZZchwZk1W+oZVKSI8ImwAOPWhJmQvL0kjYxLCOV4I 8bkiSg9+x6YCqZQw1kN6heBM5ky1zlE9EZrCRZ+Mk5tjJUrtbhQW1VL0f0WjHAgxGCUq pqtmnjgAJ0BF16z/PUe/1jJ9IOehry1QGpK63Uau0fKOUlaup5xqpAvxOQS5gzmmX1wU 4zBA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h124si9172298pfb.204.2019.08.25.21.37.53; Sun, 25 Aug 2019 21:38:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729642AbfHZEQN (ORCPT + 99 others); Mon, 26 Aug 2019 00:16:13 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:34590 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726150AbfHZEQN (ORCPT ); Mon, 26 Aug 2019 00:16:13 -0400 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 46C9D5B8E7D3174811CD; Mon, 26 Aug 2019 12:16:12 +0800 (CST) Received: from localhost (10.67.212.75) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 26 Aug 2019 12:16:10 +0800 Date: Mon, 26 Aug 2019 12:14:04 +0800 From: Kenneth Lee To: Jerome Glisse CC: Zhangfei Gao , , Greg Kroah-Hartman , , Arnd Bergmann Subject: Re: [PATCH 0/2] A General Accelerator Framework, WarpDrive Message-ID: <20190826041404.GC27955@Turing-Arch-b> References: <1565775265-21212-1-git-send-email-zhangfei.gao@linaro.org> <20190815170424.GA30916@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190815170424.GA30916@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: [10.67.212.75] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 15, 2019 at 01:04:24PM -0400, Jerome Glisse wrote: > Date: Thu, 15 Aug 2019 13:04:24 -0400 > From: Jerome Glisse > To: Zhangfei Gao > CC: linux-accelerators@lists.ozlabs.org, Greg Kroah-Hartman > , linux-kernel@vger.kernel.org, Arnd Bergmann > > Subject: Re: [PATCH 0/2] A General Accelerator Framework, WarpDrive > User-Agent: Mutt/1.11.3 (2019-02-01) > Message-ID: <20190815170424.GA30916@redhat.com> > > On Wed, Aug 14, 2019 at 05:34:23PM +0800, Zhangfei Gao wrote: > > *WarpDrive* is a general accelerator framework for the user application to > > access the hardware without going through the kernel in data path. > > > > WarpDrive is the name for the whole framework. The component in kernel > > is called uacce, meaning "Unified/User-space-access-intended Accelerator > > Framework". It makes use of the capability of IOMMU to maintain a > > unified virtual address space between the hardware and the process. > > > > WarpDrive is intended to be used with Jean Philippe Brucker's SVA > > patchset[1], which enables IO side page fault and PASID support. > > We have keep verifying with Jean's sva/current [2] > > We also keep verifying with Eric's SMMUv3 Nested Stage patch [3] > > > > This series and related zip & qm driver as well as dummy driver for qemu test: > > https://github.com/Linaro/linux-kernel-warpdrive/tree/5.3-rc1-warpdrive-v1 > > zip driver already been upstreamed. > > zip supporting uacce will be the next step. > > > > The library and user application: > > https://github.com/Linaro/warpdrive/tree/wdprd-v1-current > > Do we want a new framework ? I think that is the first question that > should be answer here. Accelerator are in many forms and so far they > never have been enough commonality to create a framework, even GPUs > with the drm is an example of that, drm only offer share framework > for the modesetting part of the GPU (as thankfully monitor connector > are not specific to GPU brands :)) > > FPGA is another example the only common code expose to userspace is > about bitstream management AFAIK. > > I would argue that a framework should only be created once there is > enough devices with same userspace API. Meanwhile you can provide > in kernel helper that allow driver to expose same API. If after a > while we have enough device driver which all use that same in kernel > helpers API then it will a good time to introduce a new framework. > Meanwhile this will allow individual device driver to tinker with > their API and maybe get to something useful to more devices in the > end. > > Note that what i propose also allow userspace code sharing for all > driver that use the same in kernel helper. > > Cheers, > J?r?me Hi, Jerome, I explain the idea here: https://zhuanlan.zhihu.com/p/79680889. We think this is a comment requirement for eveybody. Hope this can help the discussion. Thanks -- -Kenneth(Hisilicon)