From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: maarten.lankhorst@linux.intel.com, rodrigo.vivi@intel.com
Subject: [PATCH v5 0/3] Faster devcoredump and fixes
Date: Thu, 1 Aug 2024 08:41:15 -0700 [thread overview]
Message-ID: <20240801154118.2547543-1-matthew.brost@intel.com> (raw)
Combine [1] [2] for complete series to speedup devcoredump and fix it.
[1] https://patchwork.freedesktop.org/series/136541/
[2] https://patchwork.freedesktop.org/series/136545/
Matthew Brost (3):
drm/xe: Take ref to VM in delayed snapshot
drm/printer: Allow NULL data in devcoredump printer
drm/xe: Faster devcoredump
drivers/gpu/drm/drm_print.c | 13 ++-
drivers/gpu/drm/xe/xe_devcoredump.c | 111 ++++++++++++++++------
drivers/gpu/drm/xe/xe_devcoredump_types.h | 8 ++
drivers/gpu/drm/xe/xe_lrc.c | 15 ++-
include/drm/drm_print.h | 54 ++++++++++-
5 files changed, 163 insertions(+), 38 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-01 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 15:41 Matthew Brost [this message]
2024-08-01 15:41 ` [PATCH v5 1/3] drm/xe: Take ref to VM in delayed snapshot Matthew Brost
2024-08-01 15:41 ` [PATCH v5 2/3] drm/printer: Allow NULL data in devcoredump printer Matthew Brost
2024-08-01 15:41 ` [PATCH v5 3/3] drm/xe: Faster devcoredump Matthew Brost
2024-08-01 15:45 ` ✓ CI.Patch_applied: success for Faster devcoredump and fixes (rev2) Patchwork
2024-08-01 15:46 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-01 15:47 ` ✓ CI.KUnit: success " Patchwork
2024-08-01 15:59 ` ✓ CI.Build: " Patchwork
2024-08-01 16:01 ` ✓ CI.Hooks: " Patchwork
2024-08-01 16:03 ` ✗ CI.checksparse: warning " Patchwork
2024-08-01 16:22 ` ✓ CI.BAT: success " Patchwork
2024-08-01 18:56 ` ✗ 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=20240801154118.2547543-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
/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