From: Samiullah Khawaja <skhawaja@google.com>
To: 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>,
tarunsahu@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: [PATCH v3 0/1] liveupdate: Add internal APIs for file preservation
Date: Thu, 20 Aug 2026 19:18:53 +0000 [thread overview]
Message-ID: <20260820191854.1642931-1-skhawaja@google.com> (raw)
Note: Sending v3 of this as it was requested to document some of the
discussion we had on the email.
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.
v3:
- Add File Handler dependency documentation.
v2:
- rebased on liveupdate/next to resolve conflicts
- Added a note about resolution of dependencies based on offline
discussion with Pasha and David.
Pasha Tatashin (1):
liveupdate: luo_file: Add internal APIs for file preservation
include/linux/liveupdate.h | 22 +++++++++
kernel/liveupdate/luo_file.c | 84 ++++++++++++++++++++++++++++++++
kernel/liveupdate/luo_internal.h | 17 +++++++
3 files changed, 123 insertions(+)
base-commit: 3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded
--
2.55.0.766.g2966f0265a-goog
next reply other threads:[~2026-08-20 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 19:18 Samiullah Khawaja [this message]
2026-08-20 19:18 ` [PATCH v3 1/1] liveupdate: luo_file: Add internal APIs for file preservation Samiullah Khawaja
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=20260820191854.1642931-1-skhawaja@google.com \
--to=skhawaja@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=tarunsahu@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