From: Vipin Sharma <vipinsh@google.com>
To: pasha.tatashin@soleen.com, rppt@kernel.org, pratyush@kernel.org
Cc: tarunsahu@google.com, skhawaja@google.com, shuah@kernel.org,
dmatlack@google.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-kselftest@vger.kernel.org,
Vipin Sharma <vipinsh@google.com>
Subject: [PATCH v2 0/2] Make liveupdate selftests library
Date: Wed, 10 Jun 2026 16:09:06 -0700 [thread overview]
Message-ID: <20260610230909.876546-1-vipinsh@google.com> (raw)
Hello,
This is v2 series of refactoring liveupdate selftests as a library. It
exposes common liveupdate ioctls as a library which can be used by other
selftests like VFIO and IOMMU.
Currently, there are no users of this change but it is being used in
VFIO and iommu liveupdate series.
https://lore.kernel.org/kvm/20260323235817.1960573-15-dmatlack@google.com/
https://lore.kernel.org/linux-iommu/20260427175633.1978233-17-skhawaja@google.com/
I think it is better to move the patches out from the above series and
propose them as a separate series for inclusion in liveupdate repo. That
way we can decouple multiple downstream dependencies and then it can be
used by VFIO, IOMMU, and KVM (guest_memfd preservation) separately.
v2:
- Addressed Sashiko feedback regarding folder creation.
https://sashiko.dev/#/patchset/20260511201155.1488670-1-vipinsh%40google.com
- Update liveupdate.c test to use ioctl wrappers in library
v1: https://lore.kernel.org/all/20260511201155.1488670-1-vipinsh@google.com/
Vipin Sharma (2):
selftests/liveupdate: Move luo_test_utils.* into a reusable library
selftests/liveupdate: Add helpers to preserve/retrieve FDs
tools/testing/selftests/liveupdate/.gitignore | 1 +
tools/testing/selftests/liveupdate/Makefile | 14 ++----
.../include/libliveupdate.h} | 10 +++--
.../selftests/liveupdate/lib/libliveupdate.mk | 20 +++++++++
.../{luo_test_utils.c => lib/liveupdate.c} | 43 ++++++++++++++-----
.../testing/selftests/liveupdate/liveupdate.c | 40 ++++++-----------
.../selftests/liveupdate/luo_kexec_simple.c | 2 +-
.../selftests/liveupdate/luo_multi_session.c | 2 +-
.../selftests/liveupdate/luo_stress_files.c | 2 +-
.../liveupdate/luo_stress_sessions.c | 2 +-
10 files changed, 81 insertions(+), 55 deletions(-)
rename tools/testing/selftests/liveupdate/{luo_test_utils.h => lib/include/libliveupdate.h} (80%)
create mode 100644 tools/testing/selftests/liveupdate/lib/libliveupdate.mk
rename tools/testing/selftests/liveupdate/{luo_test_utils.c => lib/liveupdate.c} (91%)
base-commit: 3a358c78093f98a70d84c934b7054f636bc846f2
--
2.54.0.1099.g489fc7bff1-goog
next reply other threads:[~2026-06-10 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 23:09 Vipin Sharma [this message]
2026-06-10 23:09 ` [PATCH v2 1/2] selftests/liveupdate: Move luo_test_utils.* into a reusable library Vipin Sharma
2026-06-12 3:09 ` Pasha Tatashin
2026-06-12 17:29 ` Vipin Sharma
2026-06-10 23:09 ` [PATCH v2 2/2] selftests/liveupdate: Add helpers to preserve/retrieve FDs Vipin Sharma
2026-06-11 8:56 ` Pratyush Yadav
2026-06-12 3:09 ` Pasha Tatashin
2026-06-12 17:34 ` Vipin Sharma
2026-06-12 19:32 ` Vipin Sharma
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=20260610230909.876546-1-vipinsh@google.com \
--to=vipinsh@google.com \
--cc=dmatlack@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--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
all inboxes | Powered by JetHome®