From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Jason Miu <jasonmiu@google.com>
Cc: Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Changyuan Lyu <changyuanl@google.com>,
David Matlack <dmatlack@google.com>,
David Rientjes <rientjes@google.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v9 1/2] kho: Adopt radix tree for preserved memory tracking
Date: Sat, 7 Feb 2026 12:20:57 -0500 [thread overview]
Message-ID: <CA+CK2bD5n_fB0+--QURJgw0OKJUuCuS1zoRY==1rVjXtVC1aGg@mail.gmail.com> (raw)
In-Reply-To: <20260206021428.3386442-2-jasonmiu@google.com>
On Thu, Feb 5, 2026 at 9:14 PM Jason Miu <jasonmiu@google.com> wrote:
>
> Introduce a radix tree implementation for tracking preserved memory
> pages and switch the KHO memory tracking mechanism to use it. This
> lays the groundwork for a stateless KHO implementation that eliminates
> the need for serialization and the associated "finalize" state.
>
> This patch introduces the core radix tree data structures and
> constants to the KHO ABI. It adds the radix tree node and leaf
> structures, along with documentation for the radix tree key encoding
> scheme that combines a page's physical address and order.
>
> To support broader use by other kernel subsystems, such as hugetlb
> preservation, the core radix tree manipulation functions are exported
> as a public API.
>
> The xarray-based memory tracking is replaced with this new radix tree
> implementation. The core KHO preservation and unpreservation functions
> are wired up to use the radix tree helpers. On boot, the second kernel
> restores the preserved memory map by walking the radix tree whose root
> physical address is passed via the FDT.
>
> The ABI `compatible` version is bumped to "kho-v2" to reflect the
> structural changes in the preserved memory map and sub-FDT property
> names. This includes renaming "fdt" to "preserved-data" to better
> reflect that preserved state may use formats other than FDT.
>
> Signed-off-by: Jason Miu <jasonmiu@google.com>
> ---
> Documentation/core-api/kho/abi.rst | 6 +
> Documentation/core-api/kho/index.rst | 12 +
> include/linux/kho/abi/kexec_handover.h | 144 +++++-
> include/linux/kho_radix_tree.h | 70 +++
> kernel/liveupdate/kexec_handover.c | 651 +++++++++++++------------
> 5 files changed, 561 insertions(+), 322 deletions(-)
> create mode 100644 include/linux/kho_radix_tree.h
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Thanks,
Pasha
next prev parent reply other threads:[~2026-02-07 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 2:14 [PATCH v9 0/2] Make KHO Stateless Jason Miu
2026-02-06 2:14 ` [PATCH v9 1/2] kho: Adopt radix tree for preserved memory tracking Jason Miu
2026-02-07 17:20 ` Pasha Tatashin [this message]
2026-02-08 18:07 ` Mike Rapoport
2026-02-06 2:14 ` [PATCH v9 2/2] kho: Remove finalize state and clients Jason Miu
2026-02-07 17:20 ` Pasha Tatashin
2026-02-08 18:07 ` Mike Rapoport
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='CA+CK2bD5n_fB0+--QURJgw0OKJUuCuS1zoRY==1rVjXtVC1aGg@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=jgg@nvidia.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--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