From: Maarten@mblankhorst.nl, "Lankhorst <maarten.lankhorst"@linux.intel.com
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <dev@lankhorst.se>
Subject: [Intel-xe] [PATCH 0/4] drm/xe: Implement snapshot support.
Date: Tue, 24 Oct 2023 14:22:52 +0200 [thread overview]
Message-ID: <20231024122256.19512-1-dev@lankhorst.se> (raw)
From: Maarten Lankhorst <dev@lankhorst.se>
Hopefully at least the uapi part can be merged. This takes a coredump in
2 steps:
1. On crash, take a snapshot of the VM layout, and a reference to the
bo's to dump.
2. On readout, take a snapshot of each bo to dump and release the
reference.
Because devcoredump is done in signaling context, we can't safely
allocate a lot of memory, or do things like mmap, etc. As such, we have
to wait for readout time to map the BO and copy its contents. This means
that userspace may in the worst case overwrite data after the hang, but
hopefully this is not a serious problem.
Needs more testing..
Maarten Lankhorst (4):
drm/xe: Add uapi for dumpable bos
drm/xe: Annotate each dumpable vma as such
drm/xe: Add vm snapshot mutex for easily taking a vm snapshot during
devcoredump
drm/xe: Implement VM snapshot support
drivers/gpu/drm/xe/xe_devcoredump.c | 9 ++
drivers/gpu/drm/xe/xe_devcoredump_types.h | 2 +
drivers/gpu/drm/xe/xe_vm.c | 150 ++++++++++++++++++++--
drivers/gpu/drm/xe/xe_vm.h | 4 +
drivers/gpu/drm/xe/xe_vm_types.h | 8 ++
include/uapi/drm/xe_drm.h | 4 +
6 files changed, 169 insertions(+), 8 deletions(-)
--
2.40.1
next reply other threads:[~2023-10-24 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 12:22 Maarten, Lankhorst <maarten.lankhorst [this message]
2023-10-24 12:22 ` [Intel-xe] [PATCH 1/4] drm/xe: Add uapi for dumpable bos Maarten, Lankhorst <maarten.lankhorst
2023-11-13 21:41 ` Souza, Jose
2023-10-24 12:22 ` [Intel-xe] [PATCH 2/4] drm/xe: Annotate each dumpable vma as such Maarten, Lankhorst <maarten.lankhorst
2023-10-24 12:22 ` [Intel-xe] [PATCH 3/4] drm/xe: Add vm snapshot mutex for easily taking a vm snapshot during devcoredump Maarten, Lankhorst <maarten.lankhorst
2023-10-24 12:22 ` [Intel-xe] [PATCH 4/4] drm/xe: Implement VM snapshot support Maarten, Lankhorst <maarten.lankhorst
2023-10-27 12:17 ` Thomas Hellström
2023-10-27 17:47 ` Maarten Lankhorst
2023-11-13 21:52 ` Souza, Jose
2024-01-22 18:03 ` Souza, Jose
2023-10-24 13:07 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Implement " Patchwork
2023-10-24 13:07 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-24 13:09 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-24 13:16 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-24 13:16 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-24 13:18 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-10-24 13:52 ` [Intel-xe] ✓ CI.BAT: " 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=20231024122256.19512-1-dev@lankhorst.se \
--to=maarten@mblankhorst.nl \
--cc="Lankhorst <maarten.lankhorst"@linux.intel.com \
--cc=dev@lankhorst.se \
--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