On Wed, Aug 14, 2024 at 12:16:41PM GMT, Aravind Iddamsetty wrote:
i see that this is even called from xe_guc_exec_queue_lr_cleanup which is for long running queue
from various call paths need to check in what scenarios those happen.
Should we add a reason for long running queue?
Both of your questions would probably be answered if this was getting developed
at the same time of the user space usage of these uevents.
Can't we consider the generic Linux user as a consumer, via udevadm.
No, udevadm just confirms that there is an event being sent. Main thing
to understand here is "what is this event useful for? what can be done
as outcome of receiving this event?". From your other reply it seems
this is about "device is wedged/toast, and driver can't recover without
userspace intervention since userspace may have different policies"
What would be some examples of actions for userspace to take?
- Unbind driver, kill clients, rebind?
- FLR?
- Something else?
Is this currently implemented somewhere?
Also, is it possible to make is a generic drm event handling so distros
don't have to setup udev rules for each vendor?
Lucas De Marchi
Thanks,
Aravind.
Raag
