[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1fFRIxRq+enLWyd@nvidia.com>
Date: Tue, 25 Oct 2022 08:15:16 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Dave Airlie <airlied@...il.com>
Cc: John Hubbard <jhubbard@...dia.com>,
Oded Gabbay <ogabbay@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Daniel Vetter <daniel@...ll.ch>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Alex Deucher <alexander.deucher@....com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Yuji Ishikawa <yuji2.ishikawa@...hiba.co.jp>,
Jiho Chu <jiho.chu@...sung.com>,
Daniel Stone <daniel@...ishbar.org>,
Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>,
Jeffrey Hugo <quic_jhugo@...cinc.com>,
Christoph Hellwig <hch@...radead.org>,
Kevin Hilman <khilman@...libre.com>,
Jagan Teki <jagan@...rulasolutions.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>,
Maciej Kwapulinski <maciej.kwapulinski@...ux.intel.com>
Subject: Re: [RFC PATCH 0/3] new subsystem for compute accelerator devices
On Tue, Oct 25, 2022 at 12:27:11PM +1000, Dave Airlie wrote:
> The userspace for those is normally bespoke like ROCm, which uses
> amdkfd, and amdkfd doesn't operate like most device files from what I
> know, so I'm not sure we'd want it to operate as an accel device.
I intensely dislike this direction that drivers will create their own
char devs buried inside their device driver with no support or
supervision.
We've been here before with RDMA and it is just a complete mess.
Whatever special non-drm stuff amdkfd need to do should be supported
through the new subsystem, in a proper maintainable way.
Jason
Powered by blists - more mailing lists