linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: akpm@linux-foundation.org,  rppt@kernel.org,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	 pratyush@kernel.org
Subject: Re: [PATCH v1] liveupdate: separate memfd support into LIVEUPDATE_MEMFD
Date: Mon, 29 Dec 2025 21:51:56 +0100	[thread overview]
Message-ID: <86cy3x9fkj.fsf@kernel.org> (raw)
In-Reply-To: <20251223201506.2334991-1-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Tue, 23 Dec 2025 15:15:06 -0500")

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.

With that,

Reviewed-by: Pratyush Yadav <pratyush@kernel.org>

>  2 files changed, 16 insertions(+), 2 deletions(-)
>
[...]

-- 
Regards,
Pratyush Yadav


  reply	other threads:[~2025-12-29 20:52 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 [this message]
2025-12-30 14:54   ` 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=86cy3x9fkj.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.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