From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pratyush@kernel.org
Subject: Re: [PATCH v2] liveupdate: separate memfd support into LIVEUPDATE_MEMFD
Date: Tue, 30 Dec 2025 11:07:41 -0500 [thread overview]
Message-ID: <CA+CK2bB_7vdtWt9cccV2icV2gdyM5UaD=BnAOhWnKx9WFKWSUQ@mail.gmail.com> (raw)
In-Reply-To: <aVPwDdUpNTZ7gUT7@kernel.org>
On Tue, Dec 30, 2025 at 10:30 AM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Tue, Dec 30, 2025 at 09:53:21AM -0500, Pasha Tatashin wrote:
> > Decouple memfd preservation support from the core Live Update
> > Orchestrator configuration.
> >
> > Previously, enabling CONFIG_LIVEUPDATE forced a dependency on
> > CONFIG_SHMEM and unconditionally compiled memfd_luo.o. However, Live
> > Update may be used for purposes that do not require memfd-backed memory
> > preservation.
> >
> > Introduce CONFIG_LIVEUPDATE_MEMFD to gate memfd_luo.o. This moves the
> > SHMEM and MEMFD_CREATE dependencies to the specific feature that needs
> > them, allowing the base LIVEUPDATE option to be selected independently
> > of shared memory support.
> >
> > Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> > Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
> > ---
> > Changes v2:
> > - Updated testing config
> > - Added review-by
> >
> > kernel/liveupdate/Kconfig | 16 +++++++++++++++-
> > mm/Makefile | 2 +-
> > tools/testing/selftests/liveupdate/config | 1 +
> > 3 files changed, 17 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/liveupdate/Kconfig b/kernel/liveupdate/Kconfig
> > index d2aeaf13c3ac..9a1a8cdcf16c 100644
> > --- a/kernel/liveupdate/Kconfig
> > +++ b/kernel/liveupdate/Kconfig
> > @@ -54,7 +54,6 @@ config KEXEC_HANDOVER_ENABLE_DEFAULT
> > config LIVEUPDATE
> > bool "Live Update Orchestrator"
> > depends on KEXEC_HANDOVER
> > - depends on SHMEM
> > help
> > Enable the Live Update Orchestrator. Live Update is a mechanism,
> > typically based on kexec, that allows the kernel to be updated
> > @@ -73,4 +72,19 @@ config LIVEUPDATE
> >
> > If unsure, say N.
> >
> > +config LIVEUPDATE_MEMFD
> > + bool "Live update support for memfd"
> > + depends on LIVEUPDATE
> > + depends on MEMFD_CREATE
> > + depends on SHMEM
>
> Maybe also
>
> default LIVEUPDATE
Yeah, I like this idea, let me make the change, and send v3.
Pasha
prev parent reply other threads:[~2025-12-30 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 14:53 Pasha Tatashin
2025-12-30 15:30 ` Mike Rapoport
2025-12-30 16:07 ` Pasha Tatashin [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='CA+CK2bB_7vdtWt9cccV2icV2gdyM5UaD=BnAOhWnKx9WFKWSUQ@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@kernel.org \
--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