linux-kernel - RE: New subsystem for acceleration devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 10 Aug 2022 14:05:36 +0000
From:   <yuji2.ishikawa@...hiba.co.jp>
To:     <oded.gabbay@...il.com>, <airlied@...il.com>,
        <gregkh@...uxfoundation.org>, <jiho.chu@...sung.com>
CC:     <dri-devel@...ts.freedesktop.org>, <arnd@...db.de>,
        <linux-kernel@...r.kernel.org>, <jgg@...dia.com>
Subject: RE: New subsystem for acceleration devices

> -----Original Message-----
> From: Oded Gabbay <oded.gabbay@...il.com>
> Sent: Wednesday, August 10, 2022 6:42 AM
> To: Dave Airlie <airlied@...il.com>; Greg Kroah-Hartman
> <gregkh@...uxfoundation.org>; ishikawa yuji(石川 悠司 ○ＲＤＣ□ＡＩＴＣ○
> ＥＡ開) <yuji2.ishikawa@...hiba.co.jp>; Jiho Chu <jiho.chu@...sung.com>
> Cc: dri-devel <dri-devel@...ts.freedesktop.org>; Arnd Bergmann
> <arnd@...db.de>; Linux-Kernel@...r. Kernel. Org
> <linux-kernel@...r.kernel.org>; Jason Gunthorpe <jgg@...dia.com>
> Subject: Re: New subsystem for acceleration devices
> 
> Hi Jiho, Yuji.
> 
> I want to update that I'm currently in discussions with Dave to figure out what's
> the best way to move forward. We are writing it down to do a proper comparison
> between the two paths (new accel subsystem or using drm). I guess it will take
> a week or so.
> 
> In the meantime, I'm putting the accel code on hold. I have only managed to do
> the very basic infra and add a demo driver that shows how to register and
> unregister from it.
> You can check the code at:
> https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git/log/?h=ac
> cel
> 
> It has two commits. The first adds the subsystem code and the second adds the
> demo driver.
> The subsystem code is basically drm code copied and renamed and slightly
> modified, but I really only worked on it for a couple of hours so take that into
> consideration.
> 
> The important thing is that the demo driver shows the basic steps are really
> simple. You need to add two function calls in your probe and one function call in
> your release. Of course you will need to supply some function callbacks, but I
> haven't got to fill that in the demo driver. Once you register, you get
> /dev/accel/ac0 and
> /dev/accel/ac_controlD64 (if you want a control device). If I were to continue
> this, the next step is to do the open and close part.
> 
> I will update once we know where things are heading. As I said, I imagine it can
> take a few weeks.
> 
> Thanks,
> Oded

Hi Odded,
Thank you for uploading the framework as well as a sample. 
It's exciting to see new software is growing up.

Since Visconti DNN is a platform device, I'll write some test code to initialize driver and see if it works.

Regards,
Yuji