From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: akpm@linux-foundation.org, rppt@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v1] liveupdate: separate memfd support into LIVEUPDATE_MEMFD
Date: Tue, 30 Dec 2025 09:54:14 -0500 [thread overview]
Message-ID: <CA+CK2bA6qr8C-EtpprDZKZP9-VJyoOdZ4XHndd+GcQ66OqBVbg@mail.gmail.com> (raw)
In-Reply-To: <86cy3x9fkj.fsf@kernel.org>
On Mon, Dec 29, 2025 at 3:52 PM Pratyush Yadav <pratyush@kernel.org> wrote:
>
> Hi Pasha,
>
> On Tue, Dec 23 2025, 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.
>
> I initially didn't add a new config mainly because there was no other
> user of LUO. So disabling LIVEUPDATE_MEMFD makes LUO entirely useless.
>
> Anyway, we will eventually get other subsystems and this config will
> start making sense then. Might as well do it now.
>
> >
> > 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>
> > ---
> > kernel/liveupdate/Kconfig | 16 +++++++++++++++-
> > mm/Makefile | 2 +-
>
> I think you should also update tools/testing/selftests/liveupdate/config
> to enable this config.
Done
>
> With that,
>
> Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
Thanks.
Pasha
prev parent reply other threads:[~2025-12-30 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 20:15 Pasha Tatashin
2025-12-29 20:51 ` Pratyush Yadav
2025-12-30 14:54 ` 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+CK2bA6qr8C-EtpprDZKZP9-VJyoOdZ4XHndd+GcQ66OqBVbg@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