On Fri, Jun 13, 2025 at 09:51:27AM +0200, Pierre-Eric Pelloux-Prayer wrote: > If the theoretical overlap with client drm id is a concern, adding code to > drm_file_alloc() to not use the last 0xff ids would be easy.
Not the theoretical overlap is not of any concern for me. What I dislike is drivers silently relying on DRM API internals. > btw maybe other drivers also use kernel jobs with the same semantics, in > which case we might want to move the special IDs definition to a shared > place. Exactly, if kernel IDs are a thing we agree makes sense, we should provide a common API to properly obtain a kernel ID, regardless of whether it's an atomic or IDA.
