linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 2/2] kho: Remove finalize state and clients
Date: Sat, 7 Feb 2026 12:20:24 -0500	[thread overview]
Message-ID: <CA+CK2bBbM9__n-8JbHwi+jUaVYwue0Ro0_z1DPOCXkw5b5=vEA@mail.gmail.com> (raw)
In-Reply-To: <20260206021428.3386442-3-jasonmiu@google.com>

On Thu, Feb 5, 2026 at 9:14 PM Jason Miu <jasonmiu@google.com> wrote:
>
> Eliminate the `kho_finalize()` function and its associated state from
> the KHO subsystem. The transition to a radix tree for memory tracking
> makes the explicit "finalize" state and its serialization step
> obsolete.
>
> Remove the `kho_finalize()` and `kho_finalized()` APIs and their stub
> implementations. Update KHO client code and the debugfs interface to
> no longer call or depend on the `kho_finalize()` mechanism.
>
> Complete the move towards a stateless KHO, simplifying the overall
> design by removing unnecessary state management.
>
> Signed-off-by: Jason Miu <jasonmiu@google.com>
> ---
>  Documentation/admin-guide/mm/kho.rst        | 53 +++++----------------
>  Documentation/core-api/kho/index.rst        | 12 -----
>  kernel/liveupdate/kexec_handover.c          | 21 +-------
>  kernel/liveupdate/kexec_handover_debugfs.c  | 23 ---------
>  kernel/liveupdate/kexec_handover_internal.h |  3 --
>  kernel/liveupdate/luo_core.c                | 12 +----
>  tools/testing/selftests/kho/init.c          | 20 --------
>  7 files changed, 13 insertions(+), 131 deletions(-)

Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>

A comment in FLB patch would also need to be updated:
633  * Context: Called from liveupdate_reboot() just before
kho_finalize().
634  */
635 void luo_flb_serialize(void)

But, given that patch has not yet landed, it should be updated
separately, as it is likely this work lands first.

Pasha


  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
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 [this message]
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+CK2bBbM9__n-8JbHwi+jUaVYwue0Ro0_z1DPOCXkw5b5=vEA@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