linux-kernel - Re: Proposal: Make CONFIG_DRM_TTM_HELPER a user-configurable option

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] [day] [month] [year] [list]

Message-ID: <d78f5ee29decaf595363baf93e0b184e0a7a3177@intel.com>
Date: Fri, 15 Aug 2025 11:13:07 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: "David C. Manuelda" <stormbyte@...il.com>, linux-kernel@...r.kernel.org,
 dri-devel@...ts.freedesktop.org
Subject: Re: Proposal: Make CONFIG_DRM_TTM_HELPER a user-configurable option

On Thu, 14 Aug 2025, "David C. Manuelda" <stormbyte@...il.com> wrote:
> Hi all,
>
> I'm working with external DRM drivers (such as NVIDIA's proprietary 
> module), and I've noticed that `CONFIG_DRM_TTM_HELPER` is currently not 
> user-selectable—it gets pulled in only when enabling other drivers like 
> `nouveau`, `amdgpu`, etc.
>
> This creates a situation where, in order to build support for external 
> drivers that depend on `DRM_TTM_HELPER`, one must also enable unrelated 
> DRM drivers, which may not be desired in certain setups.
>
> In my humble opinion, it would be beneficial to make `DRM_TTM_HELPER` a 
> directly selectable option in `menuconfig`. This would allow users to 
> enable it independently, without dragging in other drivers.

You can either enable it in your .config directly, or add "select
DRM_TTM_HELPER" in the out-of-tree module.

IMO convenience for out-of-tree modules is not really a consideration,
because adding new user selectable kconfig options is an inconvenience
for in-tree users.

BR,
Jani.

-- 
Jani Nikula, Intel