✓ CI.checkpatch: success for GuC: Improve handling of the malformed G2H
Patchwork
patchwork at emeril.freedesktop.org
Tue Nov 5 17:38:42 UTC 2024
== Series Details ==
Series: GuC: Improve handling of the malformed G2H
URL : https://patchwork.freedesktop.org/series/140958/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit dd8d29addab2a9e993d2d35236888f12f9e2d96c
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date: Tue Nov 5 18:30:32 2024 +0100
drm/xe/guc: Don't treat GuC generic CAT error as protocol error
GuC uses GUC_ID_MAX if it can not map the CAT fault to any PF/VF
context. We shouldn't treat that as G2H protocol error that would
justify a GT reset, as it may happen due to some VF activity.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
Cc: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch b925cb281e79b763990ed64267ef82a87ace5060 drm-intel
8ea263d76f85 drm/xe/guc: Log content of the failed G2H message
ef569ffe3403 drm/xe/guc: Drop redundant logs about invalid G2H length
31059625466c drm/xe/guc: Don't read data from G2H prior to length check
dd8d29addab2 drm/xe/guc: Don't treat GuC generic CAT error as protocol error
More information about the Intel-xe
mailing list