On Mon Jun 22, 2026 at 7:52 PM CEST, Lyude Paul wrote: > Maybe there's a reason for you doing this I'm missing but, wouldn't it be a > better idea to simply remove the DeviceContext generic from gem objects > entirely and instead always (with the exception of Ioctl callbacks, of course) > just use the Normal context?
I did consider that, but left it as a follow-up, since it is not directly related to this patch series to drop the DeviceContext from GEM objects entirely and I thought a discussion about whether to drop it entirely is better suited for a separate patch. One thing I had in mind is that we could have TTM callbacks that guarantee us a Registered DeviceContext that could be represented by the corresonding GEM object. Of course, it could also be represented by a separate &Device<Registered> being passed to the callback. - Danilo
