On Tue, May 19, 2020 at 03:08:42PM +1000, Dave Airlie wrote: > On Fri, 15 May 2020 at 00:12, Jeffrey Hugo <jhugo@xxxxxxxxxxxxxx> wrote: > > > > Introduction: > > Qualcomm Cloud AI 100 is a PCIe adapter card which contains a dedicated > > SoC ASIC for the purpose of efficently running Deep Learning inference > > workloads in a data center environment. > > > > The offical press release can be found at - > > https://www.qualcomm.com/news/releases/2019/04/09/qualcomm-brings-power-efficient-artificial-intelligence-inference > > > > The offical product website is - > > https://www.qualcomm.com/products/datacenter-artificial-intelligence > > > > At the time of the offical press release, numerious technology news sites > > also covered the product. Doing a search of your favorite site is likely > > to find their coverage of it. > > > > It is our goal to have the kernel driver for the product fully upstream. > > The purpose of this RFC is to start that process. We are still doing > > development (see below), and thus not quite looking to gain acceptance quite > > yet, but now that we have a working driver we beleive we are at the stage > > where meaningful conversation with the community can occur. > > > Hi Jeffery, > > Just wondering what the userspace/testing plans for this driver. > > This introduces a new user facing API for a device without pointers to > users or tests for that API. > > Although this isn't a graphics driver, and Greg will likely merge > anything to the kernel you throw at him, I do wonder how to validate > the uapi from a security perspective. It's always interesting when > someone wraps a DMA engine with user ioctls, and without enough > information to decide if the DMA engine is secure against userspace > misprogramming it. Hey, I'll not merge just anything! Oh, well, maybe, if it's in staging :) > Also if we don't understand the programming API on board the device, > we can't tell if the "core" on the device are able to reprogram the > device engines either. > > Figuring this out is difficult at the best of times, it helps if there > is access to the complete device documentation or user space side > drivers in order to faciliate this. > > The other area I mention is testing the uAPI, how do you envisage > regression testing and long term sustainability of the uAPI? I agree with this request, we should have some code that we can run in order to test that things work properly. thanks, greg k-h
