[RFC PATCH 0/7] A General Accelerator Framework, WarpDrive
liguozhu at hisilicon.com
Thu Aug 2 14:05:57 AEST 2018
On Thu, Aug 02, 2018 at 02:33:12AM +0000, Tian, Kevin wrote:
> Date: Thu, 2 Aug 2018 02:33:12 +0000
> From: "Tian, Kevin" <kevin.tian at intel.com>
> To: Jerome Glisse <jglisse at redhat.com>, Kenneth Lee <nek.in.cn at gmail.com>
> CC: Hao Fang <fanghao11 at huawei.com>, Herbert Xu
> <herbert at gondor.apana.org.au>, "kvm at vger.kernel.org"
> <kvm at vger.kernel.org>, Jonathan Corbet <corbet at lwn.net>, Greg
> Kroah-Hartman <gregkh at linuxfoundation.org>, "linux-doc at vger.kernel.org"
> <linux-doc at vger.kernel.org>, "Kumar, Sanjay K" <sanjay.k.kumar at intel.com>,
> "iommu at lists.linux-foundation.org" <iommu at lists.linux-foundation.org>,
> "linux-kernel at vger.kernel.org" <linux-kernel at vger.kernel.org>,
> "linuxarm at huawei.com" <linuxarm at huawei.com>, Alex Williamson
> <alex.williamson at redhat.com>, Thomas Gleixner <tglx at linutronix.de>,
> "linux-crypto at vger.kernel.org" <linux-crypto at vger.kernel.org>, Philippe
> Ombredanne <pombredanne at nexb.com>, Zaibo Xu <xuzaibo at huawei.com>, Kenneth
> Lee <liguozhu at hisilicon.com>, "David S . Miller" <davem at davemloft.net>,
> "linux-accelerators at lists.ozlabs.org"
> <linux-accelerators at lists.ozlabs.org>
> Subject: RE: [RFC PATCH 0/7] A General Accelerator Framework, WarpDrive
> Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D191290E1A at SHSMSX101.ccr.corp.intel.com>
> > From: Jerome Glisse
> > Sent: Thursday, August 2, 2018 12:57 AM
> > On Wed, Aug 01, 2018 at 06:22:14PM +0800, Kenneth Lee wrote:
> > > From: Kenneth Lee <liguozhu at hisilicon.com>
> > >
> > > 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 remove the latency
> > > of syscall and context switch.
> > >
> > > The patchset contains documents for the detail. Please refer to it for
> > more
> > > information.
> > >
> > > This patchset is intended to be used with Jean Philippe Brucker's SVA
> > > patch  (Which is also in RFC stage). But it is not mandatory. This
> > > patchset is tested in the latest mainline kernel without the SVA patches.
> > > So it support only one process for each accelerator.
> > >
> > > With SVA support, WarpDrive can support 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: .
> > I have not fully inspected things nor do i know enough about
> > this Hisilicon ZIP accelerator to ascertain, but from glimpsing
> > at the code it seems that it is unsafe to use even with SVA due
> > to the doorbell. There is a comment talking about safetyness
> > in patch 7.
> > Exposing thing to userspace is always enticing, but if it is
> > a security risk then it should clearly say so and maybe a
> > kernel boot flag should be necessary to allow such device to
> > be use.
But doorbell is just a notification. Except for DOS (to make hardware busy) it
cannot actually take or change anything from the kernel space. And the DOS
problem can be always taken as the problem that a group of processes share the
same kernel entity.
In the coming HIP09 hardware, the doorbell will come with a random number so
only the process who allocated the queue can knock it correctly.
> > My more general question is do we want to grow VFIO to become
> > a more generic device driver API. This patchset adds a command
> > queue concept to it (i don't think it exist today but i have
> > not follow VFIO closely).
The thing is, VFIO is the only place to support DMA from user land. If we don't
put it here, we have to create another similar facility to support the same.
> > Why is that any better that existing driver model ? Where a
> > device create a device file (can be character device, block
> > device, ...). Such models also allow for direct hardware
> > access from userspace. For instance see the AMD KFD driver
> > inside drivers/gpu/drm/amd
> One motivation I guess, is that most accelerators lack of a
> well-abstracted high level APIs similar to GPU side (e.g. OpenCL
> clearly defines Shared Virtual Memory models). VFIO mdev
> might be an alternative common interface to enable SVA usages
> on various accelerators...
> > So you can already do what you are doing with the Hisilicon
> > driver today without this new infrastructure. This only need
> > hardware that have command queue and doorbell like mechanisms.
> > Unlike mdev which unify a very high level concept, it seems
> > to me spimdev just introduce low level concept (namely command
> > queue) and i don't see the intrinsic value here.
As I have said, VFIO is the only place support DMA from user space now.
> > Cheers,
> > Jérôme
> > _______________________________________________
> > iommu mailing list
> > iommu at lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/iommu
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the
information contained herein in any way (including, but not limited to, total or
partial disclosure, reproduction, or dissemination) by persons other than the
recipient(s) is prohibited. If you receive this e-mail in error, please notify
the sender by phone or email immediately and delete it!
More information about the Linux-accelerators