RFC for discussion of devcoredump uapi.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | drm/xe: Add uapi for dumpable bosdrivers/ drivers/ drivers/ +1 more | +44 | 0 replies | |
| 2/4 | drm/xe: Annotate each dumpable vma as suchdrivers/ drivers/ | +19 | 0 replies | |
| 3/4 | drm/xe: Add vm snapshot mutex for easily taking a vm snapshot during devcoredumpdrivers/ drivers/ | +12 | 2 replies | |
| 4/4 | drm/xe: Almost implement snapshot supportdrivers/ drivers/ drivers/ +1 more | +110 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Intel-xe] [PATCH 0/4] RFC for discussion of devcoredump uapi.
From: Maarten Lankhorst <[email protected]>
I think it makes a lot of sense to dump the BO's for hung processes later and not from signaling context. This way we can easily grab all locks required to dump BO state, without having to do anything in an almost atomic context.
This patch series almost implements the discussed approach, but instead of actually dumping, it only dumps the contents of a kvmalloc.
vmap dumping needs to be wired up still, but for purposes of discussion it's nearly complete.
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: Almost implement snapshot support
drivers/gpu/drm/xe/xe_bo.c | 4 + drivers/gpu/drm/xe/xe_bo.h | 1 + drivers/gpu/drm/xe/xe_devcoredump.c | 9 ++ drivers/gpu/drm/xe/xe_devcoredump_types.h | 2 + drivers/gpu/drm/xe/xe_vm.c | 140 ++++++++++++++++++++-- drivers/gpu/drm/xe/xe_vm.h | 4 + drivers/gpu/drm/xe/xe_vm_types.h | 8 ++ include/uapi/drm/xe_drm.h | 25 ++++ 8 files changed, 185 insertions(+), 8 deletions(-)
Signature · 1 line
2.40.1