From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1EE1721A447 for ; Mon, 29 Dec 2025 20:52:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767041523; cv=none; b=OVS8N2JrTpq3loVO1x0qbRx8Sof5VB3wZrVgp9fOWKQmoWD98TYhf/znlggZwN0Akj9lgqzIyP/esBBMo7RKNZwqrzGOH5rMH0pVYXKfj/VxCDXEi5zHTzz92WdIdOZCKqPWUkYPNQFGG4qKxxFYr0/aZUrywYkUB8/GsM5d9Ng= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767041523; c=relaxed/simple; bh=gf2adx8UouOcindZNtVGcyMEXzTGy6Y2QNMT5Xw5+SU=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Ln/wmEOSU1IVwDK1F99aI9Q5MvW9cwDmzst+Zz4cjWqcbBi8WFKa2hFgRNkkUYdDVQNNj6kQcc1ijWq3en4eHM4UKsbE3dTfD5hk2/fE2prXH5WUNjCM0IOp6UfiBJXVMC6x3OSwZV3TaK8P0buYwd+w2+Ojd4OwrEsQAQHEJ0I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=uYxC0MuI; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="uYxC0MuI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 69BDAC4CEF7; Mon, 29 Dec 2025 20:52:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1767041522; bh=gf2adx8UouOcindZNtVGcyMEXzTGy6Y2QNMT5Xw5+SU=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=uYxC0MuINO52iJzXziNfZI64f+MTuXZFbhFN9xjylM7RjK/84ceUORZtERiR8dJZb mdicwdgM7i+9koMC2IPgyFSxjh81NuvI/CEWHrBxljB9aVWrFoV8JrnaYi8WdcPFNk u4K+TlqT5LHUo/S/DFLKTpIZO/cI92UOJFtmbhZ2+0HdH0Zd0zP67DstJeV5UjyCg1 0czwSMk03iF0LQv18fkXUw1jsXklS4BWFnX3vPo7y69CKrcDgU5a50xMDX10CFY9+O 9M9+n0kZRMd23zHxh9fVQPiYvCGartDQtVel/cj82Y5NZ/LPv7sNoMxTXhPTLHNcan Gcrn7tVFS2t6Q== From: Pratyush Yadav To: Pasha Tatashin 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 In-Reply-To: <20251223201506.2334991-1-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Tue, 23 Dec 2025 15:15:06 -0500") References: <20251223201506.2334991-1-pasha.tatashin@soleen.com> Date: Mon, 29 Dec 2025 21:51:56 +0100 Message-ID: <86cy3x9fkj.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain 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 > --- > 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 > 2 files changed, 16 insertions(+), 2 deletions(-) > [...] -- Regards, Pratyush Yadav