Hi André, > When a device get wedged, it might be caused by a guilty application. > For userspace, knowing which app was the cause can be useful for some > situations, like for implementing a policy, logs or for giving a chance > for the compositor to let the user know what app caused the problem. > This is an optional argument, when the app info is not available, the > PID and APP string won't appear in the event string. > > Sometimes just the PID isn't enough giving that the app might be already > dead by the time userspace will try to check what was this PID's name, > so to make the life easier also notify what's the app's name in the user > event. > > Acked-by: Rodrigo Vivi <rodrigo.v...@intel.com> (for i915 and xe) > Signed-off-by: André Almeida <andrealm...@igalia.com> > --- > v3: Make comm_string and pid_string empty when there's no app info
LGTM: Reviewed-by: Krzysztof Karas <krzysztof.ka...@intel.com> Best Regards, Krzysztof
