From: Jason Miu <jasonmiu@google.com>
To: Mike Rapoport <rppt@kernel.org>
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>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v8 1/2] kho: Adopt radix tree for preserved memory tracking
Date: Thu, 5 Feb 2026 18:17:43 -0800 [thread overview]
Message-ID: <CAHN2nP+xPRYgMyhUEoBoqfwOQ4GZtvDjZf+B6JwoGe4xOSgf1A@mail.gmail.com> (raw)
In-Reply-To: <aYIfRa5fDBaLVR5y@kernel.org>
Thank you so much, Mike, I've sent out the latest version.
On Tue, Feb 3, 2026 at 8:16 AM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Thu, Jan 29, 2026 at 04:57:38PM -0800, Jason Miu wrote:
> > 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>
>
> With minor comments below
>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>
> > ---
> ...
>
> > +static int __kho_radix_walk_tree(struct kho_radix_node *root,
> > + unsigned int level, unsigned long start,
> > + kho_radix_tree_walk_callback_t cb)
> > +{
> > + struct kho_radix_node *node;
> > + struct kho_radix_leaf *leaf;
> > + unsigned long key, i;
> > + unsigned int shift;
> > + int err;
> > +
> > + for (i = 0; i < PAGE_SIZE / sizeof(phys_addr_t); i++) {
> > + if (!root->table[i])
> > + continue;
> > +
> > + shift = ((level - 1) * KHO_TABLE_SIZE_LOG2) +
> > + KHO_BITMAP_SIZE_LOG2;
> > + key = start | (i << shift);
> > +
> > + node = phys_to_virt(root->table[i]);
> > +
> > + if (level == 1) {
> > + /*
> > + * we are at level 1,
> > + * node is pointing to the level 0 bitmap.
> > + */
> > + leaf = (struct kho_radix_leaf *)node;
> > + err = kho_radix_walk_leaf(leaf, key, cb);
> > + if (err)
> > + return err;
> > + } else {
> > + err = __kho_radix_walk_tree(node, level - 1,
> > + key, cb);
> > + if (err)
> > + return err;
>
> Nit: if (err) can be moved outside if (level == 1)
>
Updated.
> > + }
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +/**
> > + * kho_radix_walk_tree - Traverses the radix tree and calls a callback for each preserved page.
> > + * @tree: A pointer to the KHO radix tree to walk.
> > + * @cb: A callback function of type kho_radix_tree_walk_callback_t that will be
> > + * invoked for each preserved page found in the tree. The callback receives
> > + * the physical address and order of the preserved page.
> > + *
> > + * This function walks the radix tree, searching from the specified top level
> > + * (@level) down to the lowest level (level 0). For each preserved page found,
>
> Hmm, why do we need @level here?
> Or it rather remained from the older versions?
>
I forgot to remove this when we changed the function signature, I've
updated it as well.
Thanks again for the guidance.
>
> --
> Sincerely yours,
> Mike.
next prev parent reply other threads:[~2026-02-06 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 0:57 [PATCH v8 0/2] Make KHO Stateless Jason Miu
2026-01-30 0:57 ` [PATCH v8 1/2] kho: Adopt radix tree for preserved memory tracking Jason Miu
2026-01-30 10:28 ` kernel test robot
2026-02-03 16:16 ` Mike Rapoport
2026-02-06 2:17 ` Jason Miu [this message]
2026-01-30 0:57 ` [PATCH v8 2/2] kho: Remove finalize state and clients Jason Miu
2026-02-03 16:18 ` 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=CAHN2nP+xPRYgMyhUEoBoqfwOQ4GZtvDjZf+B6JwoGe4xOSgf1A@mail.gmail.com \
--to=jasonmiu@google.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jgg@nvidia.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=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