All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pasha Tatashin" <pasha.tatashin@soleen.com>,
	rppt@kernel.org, kuba@kernel.org, enelsonmoore@gmail.com,
	bp@alien8.de, shuah@kernel.org, david@kernel.org,
	akpm@linux-foundation.org, ljs@kernel.org, mhocko@suse.com,
	skhan@linuxfoundation.org, vbabka@kernel.org,
	dapeng1.mi@linux.intel.com, corbet@lwn.net, surenb@google.com,
	kexec@lists.infradead.org, pratyush@kernel.org,
	rdunlap@infradead.org, elver@google.com, graf@amazon.com,
	lirongqing@baidu.com, liam@infradead.org, jlayton@kernel.org
Subject: Re: [PATCH v1 8/8] selftests: kho: add read-only KHO test to vmtest.sh
Date: Mon, 19 Oct 2026 02:19:02 +0000	[thread overview]
Message-ID: <sashiko-outbox-176525@kernel.org> (raw)
In-Reply-To: <20261019021111.990394-9-pasha.tatashin@soleen.com>

> Extend tools/testing/selftests/kho/vmtest.sh and init.c to run a second
> QEMU test verifying read-only KHO ('kho_ro=<fdt_phys>') after the
> standard KHO test on both x86_64 and aarch64:
> 
> - Build a second kernel configured with CONFIG_KEXEC_HANDOVER_READONLY=y
>   (and CONFIG_KEXEC_HANDOVER=n).
> - Pass KHO_RO_CMDLINE ('nokaslr kho_bootmem=64M,64M,64M' on x86_64,
>   'cma=116M@0x40c00000' on aarch64) to the first kernel in the read-only
>   test run so KHO allocations are placed in predictable physical ranges.
> - When booted with 'kho_ro_test', read /debugfs/kho/out/fdt_phys in
>   init.c and kexec into the read-only kernel with 'kho_ro=<fdt_phys>'
>   and architecture-specific memory parameters
>   ('memmap=792M$16M memmap=24M$1000M' on x86_64,
>   'mem=128M cma=12M@0x40000000' on aarch64) so the preserved pages are
>   excluded from the boot memory map and mapped via kho_ro_map_folio().
> - Verify 'KHO restore succeeded' from test_kho in read-only mode.
> 
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261019021111.990394-1-pasha.tatashin@soleen.com?part=8



  reply	other threads:[~2026-10-19  2:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  2:11 [PATCH v1 0/8] kho: add read-only Kexec Handover mode Pasha Tatashin
2026-10-19  2:11 ` [PATCH v1 1/8] kho: expose physical address of outgoing FDT Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 2/8] kho: move radix tree, vmalloc, and FDT helpers to internal header Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 3/8] kho: validate preservation metadata in kho_restore_vmalloc() Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 4/8] kho: do not modify incoming serialized blocks Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 5/8] kho: add read-only Kexec Handover mode Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 6/8] kho: support read-only KHO mode in kho_block Pasha Tatashin
2026-10-19  2:18   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 7/8] kho: test: support read-only KHO mode in test_kho Pasha Tatashin
2026-10-19  2:19   ` sashiko-bot
2026-10-19  2:11 ` [PATCH v1 8/8] selftests: kho: add read-only KHO test to vmtest.sh Pasha Tatashin
2026-10-19  2:19   ` sashiko-bot [this message]
2026-10-19  8:43 ` [PATCH v1 0/8] kho: add read-only Kexec Handover mode Mike Rapoport
2026-10-19 14:23   ` Pasha Tatashin

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=sashiko-outbox-176525@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=david@kernel.org \
    --cc=elver@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=graf@amazon.com \
    --cc=jlayton@kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=kuba@kernel.org \
    --cc=liam@infradead.org \
    --cc=lirongqing@baidu.com \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.