On 10/24/25 4:28 PM, Tvrtko Ursulin wrote: > On 24/10/2025 15:17, Danilo Krummrich wrote: >> On 10/24/25 3:37 PM, Tvrtko Ursulin wrote: >>> How about "unknown-driver", would that satisfy you? >> >> Honestly, the most accurate thing to say would be "fence-signaled", because >> that's the actual condition which causes the change. > Hm, ->get_driver_name() returning "fence-signaled" is not great, and debugfs > output in the form of "kernel fence: fence-signaled timeline-signaled seq 1234 > signaled" feels a bit redundant. :shrug:
Indeed, what about "retired-driver"? Still implying that it's not just unknown, but that some process has finished. But without the ambiguity of "detached-driver".
