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 019AB33A001 for ; Fri, 14 Nov 2025 17:28:00 +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=1763141281; cv=none; b=SKd0kz712IUvLXnJu1K6SEKn6k2Fhyl9lJLN8hcldQfSxpkYQR8ZpqhBEsfyhXm/TsbYCCBXOhQHHgFRLSGEC7VHEN503Naz2zg9qaGpmOfpZ0HQjtCSR51iFwbXxlUrMGbw+Vba+wXZShoNd3gH+QT01gU7i9h43iXJ9n8pLpE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763141281; c=relaxed/simple; bh=ulTWAOAR8z9do9SIRmHIYkiPa4c1m881M13St87xoQA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=U3dX/SsYPHBqK2svUAuAUd8yBBgat7OHVd17qT5etgoefFX6wTB3eaUSo+p+tlrjl285P1xkORC5/PB7cXCCrUB6uHufnbs3Q2IwgVYscCw1rLRhbUKV0PLmNfJnsFfv9PEibPY6G0pKfnIzthmUPQWPcjsN8loz9jsUKnTf2UY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dn0ywYFX; 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="dn0ywYFX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 87609C4CEF1; Fri, 14 Nov 2025 17:27:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763141280; bh=ulTWAOAR8z9do9SIRmHIYkiPa4c1m881M13St87xoQA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=dn0ywYFX7u1pMRmBB6mt3qOI+RoqX+gUyW3hryzuEn23rmHGfuVLx34qn3gdb7I7H sN+fIgiXgJzEL+gSz1mj0HFq7lITtHxpI+gru7gqIffawp8FYnhfrNEFVhx0Lin4wB eSbKoeJGcCs3KiiT0WR18L/2xpurvlBBH4UL6IYLGIpdUXqSFN+zw75W6qftHLAM58 O7XfUeBAQ5Twwq1DGqjDqssc8MacW9QvEKVbhiEvGXv2Mg8tAAG8XFsl0RJzOuDNMm sNEbe+OBiF4o72N5YbKBfYVEXjLYJK+UCR3yqYg4wmcVJCChemVNnocLYFm0BKFqha GbFfyXYii0QeA== 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 09/13] kho: Update FDT dynamically for subtree addition/removal In-Reply-To: <20251114155358.2884014-10-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 10:53:54 -0500") References: <20251114155358.2884014-1-pasha.tatashin@soleen.com> <20251114155358.2884014-10-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 18:27:57 +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, sub-FDTs were tracked in a list (kho_out.sub_fdts) and the > final FDT is constructed entirely from scratch during kho_finalize(). > > We can maintain the FDT dynamically: > 1. Initialize a valid, empty FDT in kho_init(). > 2. Use fdt_add_subnode and fdt_setprop in kho_add_subtree to > update the FDT immediately when a subsystem registers. > 3. Use fdt_del_node in kho_remove_subtree to remove entries. > > This removes the need for the intermediate sub_fdts list and the > reconstruction logic in kho_finalize(). kho_finalize() now > only needs to trigger memory map serialization. > > Signed-off-by: Pasha Tatashin Reviewed-by: Pratyush Yadav [...] -- Regards, Pratyush Yadav