[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5dxyi6z36a2vwwkw4lmh5sitgl62tneefwgnfa65pe36nvgsb4@6xzavo5itdjp>
Date: Fri, 16 May 2025 07:38:25 +0000
From: Krzysztof Karas <krzysztof.karas@...el.com>
To: André Almeida <andrealmeid@...lia.com>
CC: Alex Deucher <alexander.deucher@....com>, Christian König
<christian.koenig@....com>, <siqueira@...lia.com>, <airlied@...il.com>,
<simona@...ll.ch>, Raag Jadav <raag.jadav@...el.com>,
<rodrigo.vivi@...el.com>, <jani.nikula@...ux.intel.com>, Xaver Hugl
<xaver.hugl@...il.com>, "Pierre-Loup A . Griffais"
<pgriffais@...vesoftware.com>, <dri-devel@...ts.freedesktop.org>,
<linux-kernel@...r.kernel.org>, <kernel-dev@...lia.com>,
<amd-gfx@...ts.freedesktop.org>, <intel-xe@...ts.freedesktop.org>,
<intel-gfx@...ts.freedesktop.org>
Subject: Re: [PATCH v3 1/3] drm: Create an app info option for wedge events
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.vivi@...el.com> (for i915 and xe)
> Signed-off-by: André Almeida <andrealmeid@...lia.com>
> ---
> v3: Make comm_string and pid_string empty when there's no app info
LGTM:
Reviewed-by: Krzysztof Karas <krzysztof.karas@...el.com>
Best Regards,
Krzysztof
Powered by blists - more mailing lists