From: Mike Rapoport <rppt@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: akpm@linux-foundation.org, brauner@kernel.org, corbet@lwn.net,
graf@amazon.com, jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
masahiroy@kernel.org, ojeda@kernel.org, pratyush@kernel.org,
rdunlap@infradead.org, tj@kernel.org
Subject: Re: [PATCH v5 6/7] liveupdate: kho: move to kernel/liveupdate
Date: Wed, 15 Oct 2025 11:09:32 +0300 [thread overview]
Message-ID: <aO9WvF_WMkKKqYo5@kernel.org> (raw)
In-Reply-To: <20251007033100.836886-7-pasha.tatashin@soleen.com>
On Tue, Oct 07, 2025 at 03:30:59AM +0000, Pasha Tatashin wrote:
> Move KHO to kernel/liveupdate/ in preparation of placing all Live Update
> core kernel related files to the same place.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
One comment below.
> ---
> Documentation/core-api/kho/concepts.rst | 2 +-
> MAINTAINERS | 2 +-
> init/Kconfig | 2 ++
> kernel/Kconfig.kexec | 25 ----------------
> kernel/Makefile | 3 +-
> kernel/liveupdate/Kconfig | 30 +++++++++++++++++++
> kernel/liveupdate/Makefile | 4 +++
> kernel/{ => liveupdate}/kexec_handover.c | 6 ++--
> .../{ => liveupdate}/kexec_handover_debug.c | 0
> .../kexec_handover_internal.h | 0
> 10 files changed, 42 insertions(+), 32 deletions(-)
> create mode 100644 kernel/liveupdate/Kconfig
> create mode 100644 kernel/liveupdate/Makefile
> rename kernel/{ => liveupdate}/kexec_handover.c (99%)
> rename kernel/{ => liveupdate}/kexec_handover_debug.c (100%)
> rename kernel/{ => liveupdate}/kexec_handover_internal.h (100%)
>
> diff --git a/kernel/liveupdate/Kconfig b/kernel/liveupdate/Kconfig
> new file mode 100644
> index 000000000000..522b9f74d605
> --- /dev/null
> +++ b/kernel/liveupdate/Kconfig
> @@ -0,0 +1,30 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +
> +menu "Live Update"
KHO can be used without Live Update, let's make this "Kexec HandOver and
Live Update"
> +
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-10-15 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 3:30 [PATCH v5 0/7] liveupdate: Rework KHO for in-kernel users Pasha Tatashin
2025-10-07 3:30 ` [PATCH v5 1/7] kho: allow to drive kho from within kernel Pasha Tatashin
2025-10-15 14:36 ` Pratyush Yadav
2025-10-07 3:30 ` [PATCH v5 2/7] kho: make debugfs interface optional Pasha Tatashin
2025-10-07 3:30 ` [PATCH v5 3/7] kho: drop notifiers Pasha Tatashin
2025-10-07 3:30 ` [PATCH v5 4/7] kho: add interfaces to unpreserve folios and page ranes Pasha Tatashin
2025-10-07 3:30 ` [PATCH v5 5/7] kho: don't unpreserve memory during abort Pasha Tatashin
2025-10-07 3:30 ` [PATCH v5 6/7] liveupdate: kho: move to kernel/liveupdate Pasha Tatashin
2025-10-15 8:09 ` Mike Rapoport [this message]
2025-10-15 11:50 ` Pasha Tatashin
2025-10-16 17:30 ` Mike Rapoport
2025-10-07 3:31 ` [PATCH v5 7/7] kho: move kho debugfs directory to liveupdate 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=aO9WvF_WMkKKqYo5@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=graf@amazon.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--cc=tj@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