From: David Francis <David.Francis@amd.com>
To: <criu@lists.linux.dev>
Cc: <tvrtko.ursulin@igalia.com>, David Francis <David.Francis@amd.com>
Subject: [PATCH 0/3] Patches to allow amdgpu restore without kfd file.
Date: Fri, 10 Apr 2026 10:45:06 -0400 [thread overview]
Message-ID: <20260410144509.738903-1-David.Francis@amd.com> (raw)
These patches allow processes that have renderD device files open
but not kfd device files to dump / restore.
Mostly a proof-of-concept / baseline for future work since there's
currently no way for such a process to dump / restore its queues.
David Francis (3):
plugin/amdgpu: Add plugin to inventory even if there are no vmas
plugin/amdgpu: Add topology dump file
plugins/amdgpu: Make next_fd without kfd
plugins/amdgpu/amdgpu_plugin.c | 113 ++++++++++++++++++++++++++--
plugins/amdgpu/amdgpu_plugin_drm.c | 64 ++++++++++++++--
plugins/amdgpu/amdgpu_plugin_util.h | 9 +++
plugins/amdgpu/criu-amdgpu.proto | 5 ++
4 files changed, 180 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-10 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 14:45 David Francis [this message]
2026-04-10 14:45 ` [PATCH 1/3] plugin/amdgpu: Add plugin to inventory even if there are no vmas David Francis
2026-04-10 15:46 ` Tvrtko Ursulin
2026-04-10 16:15 ` Francis, David
2026-04-10 14:45 ` [PATCH 2/3] plugin/amdgpu: Add topology dump file David Francis
2026-04-16 14:54 ` Tvrtko Ursulin
2026-04-16 18:26 ` Francis, David
2026-04-17 9:07 ` Tvrtko Ursulin
2026-04-17 13:21 ` Francis, David
2026-04-22 13:58 ` Tvrtko Ursulin
2026-04-10 14:45 ` [PATCH 3/3] plugins/amdgpu: Make next_fd without kfd David Francis
2026-04-10 15:42 ` [PATCH 0/3] Patches to allow amdgpu restore without kfd file Tvrtko Ursulin
2026-04-10 15:46 ` Francis, David
2026-04-10 16:04 ` Tvrtko Ursulin
2026-04-10 16:12 ` Francis, David
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=20260410144509.738903-1-David.Francis@amd.com \
--to=david.francis@amd.com \
--cc=criu@lists.linux.dev \
--cc=tvrtko.ursulin@igalia.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