Show Your Support: This site is primarily supported by advertisements. Ads are what have allowed this site to be maintained on a daily basis for the past 18+ years. We do our best to ensure only clean, relevant ads are shown, when any nasty ads are detected, we work to remove them ASAP. If you would like to view the site without ads while still supporting our work, please consider our ad-free Phoronix Premium.
Linux Developers Talk Again About An Accelerator Subsystem - Or Moving Them Into The GPU/DRM Area
Stemming from the recent controversy around Habana Labs AI driver code changes (though now at least partially addressed with publishing an open-source compiler and user-space library) and how some changes have been skirted by going through "char/misc" and facing less scrutiny than if the same changes were tried to push through the GPU/DRM tree, the discussion is once again happening about where these accelerator drivers should live within the kernel.
Direct Rendering Manager drivers are interested in even moving the accelerator drivers within drivers/gpu given how similar they tend to be with non-display GPU drivers and sharing many interfaces and having common objectives. Living within the hypothetical drivers/accel was also brought up again with DRM maintainers still interested in overseeing then that new area of the kernel.
Greg KH who oversees char/misc welcomes any new reviewers and help managing the code though has questioned the drivers/gpu housing proposal and more firmly figuring out some of the new accelerator driver requirements for upstreaming.
Nothing firmly has been decided yet on an accelerator subsystem or if the GPU/DRM maintainers will oversee such accelerator drivers moving forward. Those interested in the latest discussion can see this kernel thread.