All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simona Vetter <simona.vetter@ffwll.ch>
To: David Francis <David.Francis@amd.com>
Cc: amd-gfx@lists.freedesktop.org, tvrtko.ursulin@igalia.com,
	Felix.Kuehling@amd.com, David.YatSin@amd.com,
	Chris.Freehill@amd.com, Christian.Koenig@amd.com,
	dcostantino@meta.com, sruffell@meta.com, simona@ffwll.ch,
	mripard@kernel.org, tzimmermann@suse.de,
	Alexander.Deucher@amd.com
Subject: Re: [PATCH v9] Add CRIU support for amdgpu dmabuf
Date: Thu, 31 Jul 2025 10:41:44 +0200	[thread overview]
Message-ID: <aIssSGWNP7pb4eHP@phenom.ffwll.local> (raw)
In-Reply-To: <20250725160757.231780-1-David.Francis@amd.com>

On Fri, Jul 25, 2025 at 12:07:54PM -0400, David Francis wrote:
> This patch series adds support for CRIU checkpointing of processes that
> share memory with the amdgpu dmabuf interface.
> 
> This v9 adds padding to the structs to align them.
> 
> Adding Alex Deucher beause these patches add two new amdgpu drm ioctls.

Bit aside, but I think big infrastructure stuff like CRIU support would be
good to cc to dri-devel, as an fyi. I think it's pretty ok to let the
leading driver roll this all in driver specific ways, but keeping the
wider subsystem in the loop on things like that would be good. That's also
kinda what I meant with my cc request, not cc me personally, I get _way_
too much mail myself to stay on top of anything at all.

Thanks, Sima
-- 
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      parent reply	other threads:[~2025-07-31  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 16:07 [PATCH v9] Add CRIU support for amdgpu dmabuf David Francis
2025-07-25 16:07 ` [PATCH v9 1/3] drm/amdgpu: Add CRIU ioctl to get bo info David Francis
2025-07-25 16:07 ` [PATCH v9 2/3] drm/amdgpu: Add CRIU mapping info ioctl David Francis
2025-07-25 16:07 ` [PATCH v9 3/3] drm/amdgpu: Allow kfd CRIU with no buffer objects David Francis
2025-07-31  8:41 ` Simona Vetter [this message]

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=aIssSGWNP7pb4eHP@phenom.ffwll.local \
    --to=simona.vetter@ffwll.ch \
    --cc=Alexander.Deucher@amd.com \
    --cc=Chris.Freehill@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=David.Francis@amd.com \
    --cc=David.YatSin@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dcostantino@meta.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sruffell@meta.com \
    --cc=tvrtko.ursulin@igalia.com \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.