From: Pratyush Yadav <pratyush@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Jordan Richards <jordanrichards@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Shuah Khan <shuah@kernel.org>, Jason Miu <jasonmiu@google.com>,
David Matlack <dmatlack@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 2/2] selftests/liveupdate: add end to end test infrastructure and scripts
Date: Tue, 10 Feb 2026 15:18:15 +0100 [thread overview]
Message-ID: <2vxz3438smvs.fsf@kernel.org> (raw)
In-Reply-To: <aYjVkb8qOA6yHDA7@kernel.org> (Mike Rapoport's message of "Sun, 8 Feb 2026 20:27:29 +0200")
On Sun, Feb 08 2026, Mike Rapoport wrote:
> Hi Jordan,
>
> On Thu, Feb 05, 2026 at 10:23:29PM +0000, Jordan Richards wrote:
>> From: Pasha Tatashin <pasha.tatashin@soleen.com>
>>
>> Add the end to end testing infrastructure required to verify the
>> liveupdate feature. This includes a custom init process, a test
>> orchestration script, and a batch runner.
>>
>> The framework consists of:
>>
>> init.c:
>> A lightweight init process that manages the kexec lifecycle.
>> It mounts necessary filesystems, determines the current execution
>> stage (1 or 2) via the kernel command line, and handles the
>> kexec_file_load() sequence to transition between kernels.
>>
>> luo_test.sh:
>> The primary KTAP-compliant test driver. It handles:
>> - Kernel configuration merging and building.
>> - Cross-compilation detection for x86_64 and arm64.
>> - Generation of the initrd containing the test binary and init.
>> - QEMU execution with automatic accelerator detection (KVM, HVF,
>> or TCG).
>>
>> run.sh:
>> A wrapper script to discover and execute all `luo_*.c`
>> tests across supported architectures, providing a summary of
>> pass/fail/skip results.
>>
>> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
>
> I think you also need
> Co-developed-by: Jordan Richards <jordanrichards@google.com>
>
>> Signed-off-by: Jordan Richards <jordanrichards@google.com>
>
> With nolibc fixes Thomas requested:
>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
I didn't look too closely, but at a quick skim, LGTM.
Acked-by: Pratyush Yadav (Google) <pratyush@kernel.org>
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-02-10 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 22:23 [PATCH v2 0/2] " Jordan Richards
2026-02-05 22:23 ` [PATCH v2 1/2] tools/nolibc: add ftruncate() Jordan Richards
2026-02-06 21:55 ` Thomas Weißschuh
2026-02-05 22:23 ` [PATCH v2 2/2] selftests/liveupdate: add end to end test infrastructure and scripts Jordan Richards
2026-02-06 22:06 ` Thomas Weißschuh
2026-02-09 20:56 ` Jordan Richards
2026-02-08 18:27 ` Mike Rapoport
2026-02-10 14:18 ` Pratyush Yadav [this message]
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=2vxz3438smvs.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=dmatlack@google.com \
--cc=jasonmiu@google.com \
--cc=jordanrichards@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=shuah@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