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>,
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 0/3] kho: Add support for kunit mocking KHO restore API
Date: Tue, 12 May 2026 19:51:32 +0000 [thread overview]
Message-ID: <20260512195135.804833-1-skhawaja@google.com> (raw)
To write kunit tests for preservation and restoration of liveupdate
state in various subsystems without triggering the actual kexec, the KHO
restore API needs to be mocked by the test writer. The mocking is done
to allow testing of the individual components or functions in isolation.
The patch series adds the following to support kunit testing when using the KHO
API:
- Add static stub hooks to mock the KHO restore API so the restore path
can be tested without triggering kexec.
- Add helper function that can be used by the test writer to check if
memory is preserved in KHO tree.
Finally, it adds a KUnit test for the KHO API that verifies the allocation of
preserved memory, and the preservation/restoration of pages and folios.
KHO Kunit test run:
KTAP version 1
1..1
KTAP version 1
# Subtest: kho_test
# module: kexec_handover_test
1..3
ok 1 kho_test_alloc_preserve
ok 2 kho_test_preserve_pages
ok 3 kho_test_preserve_folio
# kho_test: pass:3 fail:0 skip:0 total:3
# Totals: pass:3 fail:0 skip:0 total:3
ok 1 kho_test
Samiullah Khawaja (3):
kho: Add kunit static stubs
kho: Add helper function to check if pages are preserved
kho: Add kunit test to verify preserve/restore pages and folio
include/linux/kexec_handover.h | 5 +
kernel/liveupdate/Kconfig | 10 ++
kernel/liveupdate/Makefile | 1 +
kernel/liveupdate/kexec_handover.c | 61 ++++++++++-
kernel/liveupdate/kexec_handover_test.c | 130 ++++++++++++++++++++++++
5 files changed, 206 insertions(+), 1 deletion(-)
create mode 100644 kernel/liveupdate/kexec_handover_test.c
base-commit: 9974969c14031a097d6b45bcb7a06bb4aa525c40
--
2.54.0.563.g4f69b47b94-goog
next reply other threads:[~2026-05-12 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:51 Samiullah Khawaja [this message]
2026-05-12 19:51 ` [PATCH 1/3] kho: Add kunit static stubs Samiullah Khawaja
2026-05-12 19:51 ` [PATCH 2/3] kho: Add helper function to check if pages are preserved Samiullah Khawaja
2026-05-12 19:51 ` [PATCH 3/3] kho: Add kunit test to verify preserve/restore pages and folio 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=20260512195135.804833-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 \
/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