Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: maarten.lankhorst@linux.intel.com
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <dev@lankhorst.se>
Subject: [Intel-xe] [PATCH 0/4] RFC for discussion of devcoredump uapi.
Date: Fri, 13 Oct 2023 17:21:38 +0200	[thread overview]
Message-ID: <20231013152142.52869-1-maarten.lankhorst@linux.intel.com> (raw)

From: Maarten Lankhorst <dev@lankhorst.se>

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(-)

-- 
2.40.1


             reply	other threads:[~2023-10-13 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 15:21 maarten.lankhorst [this message]
2023-10-13 15:21 ` [Intel-xe] [PATCH 1/4] drm/xe: Add uapi for dumpable bos maarten.lankhorst
2023-10-13 15:21 ` [Intel-xe] [PATCH 2/4] drm/xe: Annotate each dumpable vma as such maarten.lankhorst
2023-10-13 15:21 ` [Intel-xe] [PATCH 3/4] drm/xe: Add vm snapshot mutex for easily taking a vm snapshot during devcoredump maarten.lankhorst
2023-10-13 19:21   ` Matthew Brost
2023-10-17 10:15     ` Maarten Lankhorst
2023-10-13 15:21 ` [Intel-xe] [PATCH 4/4] drm/xe: Almost implement snapshot support maarten.lankhorst
2023-10-13 17:23 ` [Intel-xe] ✓ CI.Patch_applied: success for RFC for discussion of devcoredump uapi Patchwork
2023-10-13 17:23 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-13 17:24 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-13 17:31 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-13 17:32 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-13 17:33 ` [Intel-xe] ✓ CI.checksparse: " 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=20231013152142.52869-1-maarten.lankhorst@linux.intel.com \
    --to=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