linux-kernel - Re: [RFC PATCH 0/3] new subsystem for compute accelerator 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: <Y1fz89kib4zVuqn5@nvidia.com>
Date:   Tue, 25 Oct 2022 11:34:27 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Alex Deucher <alexdeucher@...il.com>
Cc:     Dave Airlie <airlied@...il.com>,
        Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>,
        Jiho Chu <jiho.chu@...sung.com>,
        Jeffrey Hugo <quic_jhugo@...cinc.com>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Arnd Bergmann <arnd@...db.de>,
        John Hubbard <jhubbard@...dia.com>,
        Oded Gabbay <ogabbay@...nel.org>, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org,
        Christoph Hellwig <hch@...radead.org>,
        Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Alex Deucher <alexander.deucher@....com>,
        Yuji Ishikawa <yuji2.ishikawa@...hiba.co.jp>,
        Kevin Hilman <khilman@...libre.com>,
        Maciej Kwapulinski <maciej.kwapulinski@...ux.intel.com>,
        Jagan Teki <jagan@...rulasolutions.com>
Subject: Re: [RFC PATCH 0/3] new subsystem for compute accelerator devices

On Tue, Oct 25, 2022 at 10:21:34AM -0400, Alex Deucher wrote:

> E.g., the kfd node provides platform level compute
> topology information; e.g., the NUMA details for connected GPUs and
> CPUs, non-GPU compute node information, cache level topologies, etc.

See, this is exactly what I'm talking about. What on earth does any of
this have to do with DRM?

We alread have places in the kernel that own and expose these kinds of
information, drivers need to use them. Not re-invent them.

Jason