[PATCH v5 0/3] drm/xe: Add devcoredump locking and reason string
John.C.Harrison at Intel.com
John.C.Harrison at Intel.com
Tue Nov 26 19:18:54 UTC 2024
From: John Harrison <John.C.Harrison at Intel.com>
There are now many ways to trigger a devcoredump capture. So include a
reason message to say why it happened.
Also, add locking to avoid a races with double captures and free vs read.
v2: Change to spin_lock to mutex and a few other tweaks (review
feedback from Matthew Brost).
v3: Move mutex locks and add reclaim annotation (review feedback from
Matthew Brost).
v4: Fix typo - when adding lockdep specific code it helps to actually
have CONFIG_LOCKDEP enabled!
v5: New patch to move the call to dev_coredumpm_timeout to prevent an
existing issue highlighted by the new lockdep checking.
Signed-off-by: John Harrison <John.C.Harrison at Intel.com>
John Harrison (3):
drm/xe: Add a reason string to the devcoredump
drm/xe: Move the coredump registration to the worker thread
drm/xe: Add mutex locking to devcoredump
drivers/gpu/drm/xe/xe_devcoredump.c | 115 +++++++++++++++-------
drivers/gpu/drm/xe/xe_devcoredump.h | 5 +-
drivers/gpu/drm/xe/xe_devcoredump_types.h | 8 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 14 ++-
4 files changed, 102 insertions(+), 40 deletions(-)
--
2.47.0
More information about the Intel-xe
mailing list