CRIU (Checkpoint/Restore in Userspace) mailing list
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: Andrei Vagin <avagin@google.com>
Cc: criu@lists.linux.dev,
	Radostin Stoyanov <rstoyanov@fedoraproject.org>,
	David Francis <David.Francis@amd.com>
Subject: Re: [PATCH v2 00/23] Amdgpu plugin cleanups and fixes
Date: Mon, 13 Apr 2026 20:47:17 +0100	[thread overview]
Message-ID: <85ea39dc-48e2-41cc-8d0c-b96e76ec9f46@igalia.com> (raw)
In-Reply-To: <CAEWA0a609NGMDjDXEfPvJABh5E-88VPA8oXrEtok=1kcpZvUpA@mail.gmail.com>


Hi Andrei,

On 13/04/2026 19:23, Andrei Vagin wrote:
> On Fri, Apr 10, 2026 at 11:55 AM Tvrtko Ursulin
> <tvrtko.ursulin@igalia.com> wrote:
>>
>> This series is a subset of previously posted as RFC:
>> https://lore.kernel.org/criu/CAEWA0a4ghpPeQjg1ETiQysGj5agfWwJRvMbWzhrYL5r8WZ5H7Q@mail.gmail.com/T/#mfb4ab4866a0cb440961be7170d0e107fab7eedf2
>>
>> And as v1 cleanups only:
>> https://lore.kernel.org/criu/5e99e181-6e19-4b7d-8c10-a846ed4e74a3@igalia.com/T/#md4284ded141876b7d7b942d2d449d6100bd20a2e
>>
>> It still only contains the fixes and cleanups with the render node hacks
>> removed.
>>
>> All patches have now been reviewed, although from v1 to v2 it was a difficult
>> rebase do upstream movement that happened in the meantime. So I think it would
>> be good to smoke test it in an environemnt other than where I tested using my
>> amd_criu IGT.
>>
>> Two patches have been dropped from the series:
>>
>>    plugins/amdgpu: Check images were opened successfully
>>    plugins/amdgpu: Fix error handling in amdgpu_plugin_drm_restore_file()
>>
>> The same fixes have since been implemented in upstream at least in:
>>
>>    611af0188dfe ("plugin/amdgpu: add open_img_file error handling")
>>    16b252ee21a8 ("plugin/amdgpu: add missing xzalloc() NULL checks in drm")
>>
>> Fingers crossed I have not messed up anything in this relatively extensive
>> rebase and ideally we can merge this sooner rather than later and carry on
>> working on top.
> 
> Tvrtko,
> 
> could you please review comments and ci failures:
> https://github.com/checkpoint-restore/criu/pull/2999

Sure thing, I was not aware there is all that infra. Also, if I switch 
away from the mailing list workflow, presumably I can get these reports 
for pull requests I make?

Regards,

Tvrtko


  reply	other threads:[~2026-04-13 19:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 18:54 [PATCH v2 00/23] Amdgpu plugin cleanups and fixes Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 01/23] plugins/amgdpu: Fix one error message Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 02/23] plugins/amdgpu: Remove unused current_pid global variable Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 03/23] plugins/amdgpu: Remove unused new_minor from struct vma_metadata Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 04/23] plugins/amdgpu: Fix drm pages size header Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 05/23] plugins/amdgpu: Fix logging of failures to open files during restore init Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 06/23] plugins/amdgpu: Propagate failure to save buffer object content Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 07/23] plugins/amdgpu: Close the directory when image probing fails Tvrtko Ursulin
2026-04-10 18:54 ` [PATCH v2 08/23] plugins/amdgpu: Close dma-buf image file if the read fails Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 09/23] plugins/amdgpu: Flatten amdgpu_restore_init a bit Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 10/23] plugins/amdgpu: Add error handling for seek operations Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 11/23] plugins/amdgpu: Consolidate vm_info collection Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 12/23] plugins/amdgpu: Remove plugin_log_msg() Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 13/23] plugins/amdgpu: Reduce amount of debug logging a little bit Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 14/23] plugins/amdgpu: Do not eat the errno in kmtIoctl Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 15/23] plugins/amdgpu: Fix open_drm_render_device() Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 16/23] plugins/amdgpu: Check sdma operation type early and once Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 17/23] plugins/amdgpu: Add plugin to inventory even if process has no vmas Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 18/23] plugins/amdgpu: Move drm file dump and restore into helpers Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 19/23] plugins/amdgpu: Use the load_img helper in drm file restore Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 20/23] plugins/amdgpu: Convert away from libc buffered file IO Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 21/23] plugins/amdgpu: Use save_vma_updates for all call sites Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 22/23] plugins/amdgpu: amdgpu_plugin_drm_restore_file() does not need to use libdrm Tvrtko Ursulin
2026-04-10 18:55 ` [PATCH v2 23/23] plugins/amdgpu: Fix remaining wrong usages of pr_perror Tvrtko Ursulin
2026-04-13 18:23 ` [PATCH v2 00/23] Amdgpu plugin cleanups and fixes Andrei Vagin
2026-04-13 19:47   ` Tvrtko Ursulin [this message]
2026-04-13 20:03     ` Andrei Vagin

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=85ea39dc-48e2-41cc-8d0c-b96e76ec9f46@igalia.com \
    --to=tvrtko.ursulin@igalia.com \
    --cc=David.Francis@amd.com \
    --cc=avagin@google.com \
    --cc=criu@lists.linux.dev \
    --cc=rstoyanov@fedoraproject.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