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 115CB1FF7C7 for ; Fri, 14 Nov 2025 16:32:56 +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=1763137976; cv=none; b=SxTQX8C/KXGCX7mHqp3yBxtW+A2SLGXrmrzXfd/XkFF2ndVrvCkAH4xP0l4sgu8scVcAKXuyFSbWK+8JzEscY/3n6Q0FYxI/4V7Fb3jXcOmnhks4mmbKbMusuGtcyx9G2InWf0SeevMq0sPIHR7j80FzbdF3DB9HQKrm9ttYIaE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763137976; c=relaxed/simple; bh=fy9goWnm4WyDrFh6uM2Y7bCHkbvkrMLy5j0RbsMDiTQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=RRtHH3FLh/ttIZuVtZr9aaINKvFmZWJZKNBD+v6z9pIioQA/nEdcLKJ6LcAkAizGpBrqx5XbLO8F/B+bkWzWbH8x1FI/VtxGyR9FcLVEfPX3Pd23R+Qv8lrHQ2UjbMBX+XaDlhm4Vraw5TDNtebYfJe0nlBJiYS47sENxqi3dtQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=VFeoJ6AE; 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="VFeoJ6AE" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0FB46C4CEF1; Fri, 14 Nov 2025 16:32:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763137975; bh=fy9goWnm4WyDrFh6uM2Y7bCHkbvkrMLy5j0RbsMDiTQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=VFeoJ6AE+ab565fJGL0NyGcL684TvXpyQDHI0jD/X4tc9MmYPcp8rhjUchr38DYrC MlI2XwZfDQ+P7jMolPtXjOxmTwQQY8I7nvHAdffhTA2EMP65mqswANw4qJDeGRTyoh dOMoEMNKxP24ISiCp3Sq0qKO+N9hkDgNU3n0l3DEeyOL0Cb/ydyjHxyqzPr1MeIO3b QtG8Y8+hSi6VLjaDZu0KmoJb9ZhqJuk59kasYggKZrt+NI4Zxw6CeNUEGhUQg54ETu 2iIQHOl7RFQP+20PonMZKaD0vpTepVwssKwzQmTalxR6HsH1lHzEbccJJ+YiVmKE5X RFrxGbK7LM1kw== From: Pratyush Yadav To: Pasha Tatashin Cc: akpm@linux-foundation.org, bhe@redhat.com, rppt@kernel.org, jasonmiu@google.com, arnd@arndb.de, coxu@redhat.com, dave@vasilevsky.ca, ebiggers@google.com, graf@amazon.com, kees@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, linux-mm@kvack.org Subject: Re: [PATCH v1 03/13] kho: Preserve FDT folio only once during initialization In-Reply-To: <20251114155358.2884014-4-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 10:53:48 -0500") References: <20251114155358.2884014-1-pasha.tatashin@soleen.com> <20251114155358.2884014-4-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 17:32:52 +0100 Message-ID: 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 On Fri, Nov 14 2025, Pasha Tatashin wrote: > Currently, the FDT folio is preserved inside __kho_finalize(). If the > user performs multiple finalize/abort cycles, kho_preserve_folio() is > called repeatedly for the same FDT folio. > > Since the FDT folio is allocated once during kho_init(), it should be > marked for preservation at the same time. Move the preservation call to > kho_init() to align the preservation state with the object's lifecycle > and simplify the finalize path. > > Signed-off-by: Pasha Tatashin Reviewed-by: Pratyush Yadav [...] -- Regards, Pratyush Yadav