From: Mike Rapoport <rppt@kernel.org>
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
pasha.tatashin@soleen.com, pratyush@kernel.org, graf@amazon.com,
shuah@kernel.org, guoren@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: [PATCH v3 4/4] selftests: liveupdate: Add riscv support
Date: Sun, 8 Nov 2026 13:16:51 +0200 [thread overview]
Message-ID: <avBaI9bFdoOnZzGp@kernel.org> (raw)
In-Reply-To: <20261106071459.2003-5-cp0613@linux.alibaba.com>
On Fri, Nov 06, 2026 at 03:14:59PM +0800, Chen Pei wrote:
> Teach the live update vmtest runners about riscv64, so the LUO tests can
> be run on this architecture.
>
> LIVEUPDATE depends only on KEXEC_HANDOVER, enabled for riscv64 by the
> previous commit, so nothing in the tests stood in the way.
>
> Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> tools/testing/selftests/liveupdate/config.riscv64 | 3 +++
> tools/testing/selftests/liveupdate/run-vmtests.sh | 2 +-
> tools/testing/selftests/liveupdate/vmtest.sh | 8 +++++++-
> 3 files changed, 11 insertions(+), 2 deletions(-)
> create mode 100644 tools/testing/selftests/liveupdate/config.riscv64
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-11-08 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 7:14 [PATCH v3 0/4] riscv: Enable kexec handover and live update Chen Pei
2026-11-06 7:14 ` [PATCH v3 1/4] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-11-06 7:14 ` [PATCH v3 2/4] riscv: Add support for kexec handover (KHO) Chen Pei
2026-11-06 7:14 ` [PATCH v3 3/4] selftests: kho: Add riscv support Chen Pei
2026-11-08 11:16 ` Mike Rapoport
2026-11-06 7:14 ` [PATCH v3 4/4] selftests: liveupdate: " Chen Pei
2026-11-08 11:16 ` Mike Rapoport [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=avBaI9bFdoOnZzGp@kernel.org \
--to=rppt@kernel.org \
--cc=alex@ghiti.fr \
--cc=cp0613@linux.alibaba.com \
--cc=graf@amazon.com \
--cc=guoren@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@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
all inboxes | Powered by JetHome®