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]

Message-Id: <20220803022549.cc12d4b82fb05974214f8b23@samsung.com>
Date:   Wed, 3 Aug 2022 02:25:49 +0900
From:   Jiho Chu <jiho.chu@...sung.com>
To:     Oded Gabbay <oded.gabbay@...il.com>
Cc:     Yuji Ishikawa <yuji2.ishikawa@...hiba.co.jp>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>,
        "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: New subsystem for acceleration devices

On Sun, 31 Jul 2022 14:45:34 +0300
Oded Gabbay <oded.gabbay@...il.com> wrote:

> Hi,
> Greg and I talked a couple of months ago about preparing a new accel
> subsystem for compute/acceleration devices that are not GPUs and I
> think your drivers that you are now trying to upstream fit it as well.
> 
> Would you be open/interested in migrating your drivers to this new subsystem ?
> 
> Because there were no outstanding candidates, I have done so far only
> a basic and partial implementation of the infrastructure for this
> subsystem, but if you are willing to join I believe I can finish it
> rather quickly.
> 
> At start, the new subsystem will provide only a common device
> character (e.g. /dev/acX) so everyone will do open/close/ioctl on the
> same device character. Also sysfs/debugfs entries will be under that
> device and maybe an IOCTL to retrieve information.
> 
> In the future I plan to move some of habanalabs driver's code into the
> subsystem itself, for common tasks such as memory management, dma
> memory allocation, etc.
> 
> Of course, you will be able to add your own IOCTLs as you see fit.
> There will be a range of IOCTLs which are device-specific (similar to
> drm).
> 
> wdyt ?
> 
> Thanks,
> Oded
> 

Hi, Oded.
Thanks for sharing your idea. And I'm really positive on the subsystem for ai acceleration devices.

Samsung NPU driver is trying to upstream now, so I wonder new subsystem can cover all of the operations.
I'll appreciate if you share the code when you ready, so I can figure out our driver can be migrated.

Sincerely,
Jiho Chu