From: Jerome Glisse Subject: Re: [RFCv2 PATCH 0/7] A General Accelerator Framework, WarpDrive Date: Thu, 6 Sep 2018 09:31:33 -0400 Message-ID: <20180906133133.GA3830@redhat.com> References: <20180903005204.26041-1-nek.in.cn@gmail.com> <20180904150019.GA4024@redhat.com> <20180904101509.62314b67@t450s.home> <20180906094532.GG230707@Turing-Arch-b> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Alex Williamson , Kenneth Lee , Jonathan Corbet , Herbert Xu , "David S . Miller" , Joerg Roedel , Hao Fang , Zhou Wang , Zaibo Xu , Philippe Ombredanne , Greg Kroah-Hartman , Thomas Gleixner , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, iommu@lists.linux-foundation.org, kvm@vger.kernel.org, linux-accelerators@lists.ozlabs.org, Lu Baolu , Sanjay Kumar , linuxarm@huawei.com To: Kenneth Lee Return-path: Content-Disposition: inline In-Reply-To: <20180906094532.GG230707@Turing-Arch-b> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Thu, Sep 06, 2018 at 05:45:32PM +0800, Kenneth Lee wrote: > On Tue, Sep 04, 2018 at 10:15:09AM -0600, Alex Williamson wrote: > > Date: Tue, 4 Sep 2018 10:15:09 -0600 > > From: Alex Williamson > > To: Jerome Glisse > > CC: Kenneth Lee , Jonathan Corbet , > > Herbert Xu , "David S . Miller" > > , Joerg Roedel , Kenneth Lee > > , Hao Fang , Zhou Wang > > , Zaibo Xu , Philippe > > Ombredanne , Greg Kroah-Hartman > > , Thomas Gleixner , > > linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, > > linux-crypto@vger.kernel.org, iommu@lists.linux-foundation.org, > > kvm@vger.kernel.org, linux-accelerators@lists.ozlabs.org, Lu Baolu > > , Sanjay Kumar , > > linuxarm@huawei.com > > Subject: Re: [RFCv2 PATCH 0/7] A General Accelerator Framework, WarpDrive > > Message-ID: <20180904101509.62314b67@t450s.home> > > > > On Tue, 4 Sep 2018 11:00:19 -0400 > > Jerome Glisse wrote: > > > > > On Mon, Sep 03, 2018 at 08:51:57AM +0800, Kenneth Lee wrote: > > > > From: Kenneth Lee > > > > > > > > WarpDrive is an accelerator framework to expose the hardware capabilities > > > > directly to the user space. It makes use of the exist vfio and vfio-mdev > > > > facilities. So the user application can send request and DMA to the > > > > hardware without interaction with the kernel. This removes the latency > > > > of syscall. > > > > > > > > WarpDrive is the name for the whole framework. The component in kernel > > > > is called SDMDEV, Share Domain Mediated Device. Driver driver exposes its > > > > hardware resource by registering to SDMDEV as a VFIO-Mdev. So the user > > > > library of WarpDrive can access it via VFIO interface. > > > > > > > > The patchset contains document for the detail. Please refer to it for more > > > > information. > > > > > > > > This patchset is intended to be used with Jean Philippe Brucker's SVA > > > > patch [1], which enables not only IO side page fault, but also PASID > > > > support to IOMMU and VFIO. > > > > > > > > With these features, WarpDrive can support non-pinned memory and > > > > multi-process in the same accelerator device. We tested it in our SoC > > > > integrated Accelerator (board ID: D06, Chip ID: HIP08). A reference work > > > > tree can be found here: [2]. > > > > > > > > But it is not mandatory. This patchset is tested in the latest mainline > > > > kernel without the SVA patches. So it supports only one process for each > > > > accelerator. > > > > > > > > We have noticed the IOMMU aware mdev RFC announced recently [3]. > > > > > > > > The IOMMU aware mdev has similar idea but different intention comparing to > > > > WarpDrive. It intends to dedicate part of the hardware resource to a VM. > > > > And the design is supposed to be used with Scalable I/O Virtualization. > > > > While sdmdev is intended to share the hardware resource with a big amount > > > > of processes. It just requires the hardware supporting address > > > > translation per process (PCIE's PASID or ARM SMMU's substream ID). > > > > > > > > But we don't see serious confliction on both design. We believe they can be > > > > normalized as one. > > > > > > > > > > So once again i do not understand why you are trying to do things > > > this way. Kernel already have tons of example of everything you > > > want to do without a new framework. Moreover i believe you are > > > confuse by VFIO. To me VFIO is for VM not to create general device > > > driver frame work. > > > > VFIO is a userspace driver framework, the VM use case just happens to > > be a rather prolific one. VFIO was never intended to be solely a VM > > device interface and has several other userspace users, notably DPDK > > and SPDK, an NVMe backend in QEMU, a userspace NVMe driver, a ruby > > wrapper, and perhaps others that I'm not aware of. Whether vfio is > > appropriate interface here might certainly still be a debatable topic, > > but I would strongly disagree with your last sentence above. Thanks, > > > > Alex > > > > Yes, that is also my standpoint here. > > > > So here is your use case as i understand it. You have a device > > > with a limited number of command queues (can be just one) and in > > > some case it can support SVA/SVM (when hardware support it and it > > > is not disabled). Final requirement is being able to schedule cmds > > > from userspace without ioctl. All of this exists already exists > > > upstream in few device drivers. > > > > > > > > > So here is how every body else is doing it. Please explain why > > > this does not work. > > > > > > 1 Userspace open device file driver. Kernel device driver create > > > a context and associate it with on open. This context can be > > > uniq to the process and can bind hardware resources (like a > > > command queue) to the process. > > > 2 Userspace bind/acquire a commands queue and initialize it with > > > an ioctl on the device file. Through that ioctl userspace can > > > be inform wether either SVA/SVM works for the device. If SVA/ > > > SVM works then kernel device driver bind the process to the > > > device as part of this ioctl. > > > 3 If SVM/SVA does not work userspace do an ioctl to create dma > > > buffer or something that does exactly the same thing. > > > 4 Userspace mmap the command queue (mmap of the device file by > > > using informations gather at step 2) > > > 5 Userspace can write commands into the queue it mapped > > > 6 When userspace close the device file all resources are release > > > just like any existing device drivers. > > Hi, Jerome, > > Just one thing, as I said in the cover letter, dma-buf requires the application > to use memory created by the driver for DMA. I did try the dma-buf way in > WrapDrive (refer to [4] in the cover letter), it is a good backup for NOIOMMU > mode or we cannot solve the problem in VFIO. > > But, in many of my application scenario, the application already has some memory > in hand, maybe allocated by the framework or libraries. Anyway, they don't get > memory from my library, and they pass the poiter for data operation. And they > may also have pointer in the buffer. Those pointer may be used by the > accelerator. So I need hardware fully share the address space with the > application. That is what dmabuf cannot do. dmabuf can do that ... it is call uptr you can look at i915 for instance. Still this does not answer my question above, why do you need to be in VFIO to do any of the above thing ? Kernel has tons of examples that does all of the above and are not in VFIO (including usinng existing user pointer with device). Cheers, J?r?me