From: tarunsahu@google.com
To: Samiullah Khawaja <skhawaja@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>
Cc: Samiullah Khawaja <skhawaja@google.com>,
David Matlack <dmatlack@google.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:KEXEC HANDOVER (KHO)" <kexec@lists.infradead.org>,
"open list:KEXEC HANDOVER (KHO)" <linux-mm@kvack.org>
Subject: Re: [PATCH 0/1] liveupdate: Add internal APIs for file preservation
Date: Mon, 15 Jun 2026 12:28:59 +0000 [thread overview]
Message-ID: <9huz4ij4xa0k.fsf@tarunix.c.googlers.com> (raw)
In-Reply-To: <20260613012521.835490-1-skhawaja@google.com>
Hi,
Thankyou for sending it saperately, Now I can remove this from
guest_memfd series, And we can track it here.
I think it needs rebasing. I see it fails to apply to liveupdate/next
and mainline both.
Thanks
Samiullah Khawaja <skhawaja@google.com> writes:
> Live update orchestrator file handlers depend on the preservation of
> other files. To make sure that the dependency is preserved, the file
> handlers needs to fetch the preservation token of the preserved
> dependency. Similarly during restore, a file handler wants to fetch the
> restored file of the dependency.
>
> There are two known usecases of this,
>
> - VFIO-Cdev preservation requires the preservation of iommufd. This is
> required by the IOMMU preservation series:
> https://lore.kernel.org/all/20260427175633.1978233-1-skhawaja@google.com/
> - guest_memfd preservation requires the preservation of kvmfd. This is
> required by the guest_memfd preservation series:
> https://lore.kernel.org/all/20ae20f9d1a198b289444ebb4c824314cbba1bcf.1780676742.git.tarunsahu@google.com/
>
> This patch was being sent as part of the IOMMU preservation series, but
> now it is being sent separately.
>
> Pasha Tatashin (1):
> liveupdate: luo_file: Add internal APIs for file preservation
>
> include/linux/liveupdate.h | 21 ++++++++++
> kernel/liveupdate/luo_file.c | 69 ++++++++++++++++++++++++++++++++
> kernel/liveupdate/luo_internal.h | 17 ++++++++
> 3 files changed, 107 insertions(+)
>
> base-commit: 34e8f02817e31826e76bb2ded48bf28fe921f20b
> --
> 2.54.0.1136.gdb2ca164c4-goog
next prev parent reply other threads:[~2026-06-15 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 1:25 Samiullah Khawaja
2026-06-13 1:25 ` [PATCH 1/1] liveupdate: luo_file: " Samiullah Khawaja
2026-06-14 12:48 ` Pranjal Shrivastava
2026-06-26 11:57 ` Pratyush Yadav
2026-06-29 7:32 ` Pasha Tatashin
2026-06-29 9:08 ` Pratyush Yadav
2026-06-29 16:50 ` Pratyush Yadav
2026-07-06 19:59 ` Samiullah Khawaja
2026-07-17 17:24 ` Pratyush Yadav
2026-07-18 0:36 ` Samiullah Khawaja
2026-06-15 12:28 ` tarunsahu [this message]
2026-06-17 19:00 ` [PATCH 0/1] liveupdate: " Mike Rapoport
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=9huz4ij4xa0k.fsf@tarunix.c.googlers.com \
--to=tarunsahu@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=skhawaja@google.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