From: Mike Rapoport <rppt@kernel.org>
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>,
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 v3 0/4] Make KHO Stateless
Date: Sat, 3 Jan 2026 20:59:49 +0200 [thread overview]
Message-ID: <aVlnJZ7vN6-FEL6z@kernel.org> (raw)
In-Reply-To: <20251209025317.3846938-1-jasonmiu@google.com>
On Mon, Dec 08, 2025 at 06:53:12PM -0800, Jason Miu wrote:
>
> This series is broken down into the following patches:
>
> 1. kho: Introduce KHO FDT ABI header:
> Adds a dedicated ABI header to define the FDT interface.
>
> 2. kho: Relocate vmalloc preservation structure to KHO ABI header
> Adds `struct kho_vmalloc` and related structs to the ABI header.
I think these two can be merged independently of the radix tree change.
They seem ready to me and having them upstream will make it easier for new
KHO functionality, like e.g. "kexec history" patches
(https://lore.kernel.org/all/20260102-kho-v2-0-1747b1a3a1d6@debian.org)
I'm going to prepare a series with these two patches and some few more
updates to KHO and LUO docs and I'll send them in the next few days.
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-01-03 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 2:53 Jason Miu
2025-12-09 2:53 ` [PATCH v3 1/4] kho: Introduce KHO FDT ABI header Jason Miu
2025-12-09 2:53 ` [PATCH v3 2/4] kho: Relocate vmalloc preservation structure to KHO " Jason Miu
2025-12-09 2:53 ` [PATCH v3 3/4] kho: Adopt radix tree for preserved memory tracking Jason Miu
2026-01-05 9:27 ` Mike Rapoport
2025-12-09 2:53 ` [PATCH v3 4/4] kho: Remove finalize state and clients Jason Miu
2026-01-03 18:59 ` 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=aVlnJZ7vN6-FEL6z@kernel.org \
--to=rppt@kernel.org \
--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=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
/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