From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v2 0/2] drm/xe: Add devcoredump locking and reason string
Date: Thu, 21 Nov 2024 14:55:40 -0800 [thread overview]
Message-ID: <20241121225542.1336796-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@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).
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/xe: Add a reason string to the devcoredump
drm/xe: Add mutex locking to devcoredump
drivers/gpu/drm/xe/xe_devcoredump.c | 47 ++++++++++++++++++++---
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, 62 insertions(+), 12 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-21 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 22:55 John.C.Harrison [this message]
2024-11-21 22:55 ` [PATCH v2 1/2] drm/xe: Add a reason string to the devcoredump John.C.Harrison
2024-11-21 22:55 ` [PATCH v2 2/2] drm/xe: Add mutex locking to devcoredump John.C.Harrison
2024-11-21 23:44 ` Matthew Brost
2024-11-22 1:25 ` John Harrison
2024-11-22 2:01 ` Matthew Brost
2024-11-22 21:00 ` John Harrison
2024-11-22 22:25 ` Matthew Brost
2024-11-22 0:13 ` ✓ CI.Patch_applied: success for drm/xe: Add devcoredump locking and reason string (rev2) Patchwork
2024-11-22 0:14 ` ✓ CI.checkpatch: " Patchwork
2024-11-22 0:15 ` ✓ CI.KUnit: " Patchwork
2024-11-22 0:33 ` ✓ CI.Build: " Patchwork
2024-11-22 0:35 ` ✓ CI.Hooks: " Patchwork
2024-11-22 0:36 ` ✓ CI.checksparse: " Patchwork
2024-11-22 1:00 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-22 18:53 ` ✗ Xe.CI.Full: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241121225542.1336796-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox