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 E54A533436D for ; Fri, 14 Nov 2025 17:11:42 +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=1763140303; cv=none; b=DF9BuSZTDDkcxzU2dgHP0F2jEEQggrSB9874It72dZq32aYINbu5M9LXwlbwj8rs9bAQNDimpOjlQ9ouP+6wQ8xRzYPvVNVOW23lOsXWSLihT2uMw5rYkI/aEX0G3OHLMYZIfiXMHzBE+naf6/K+qw857bGc+VAM0oZuow6IBHM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763140303; c=relaxed/simple; bh=KdPt1kVDnO95rsL6NNliJLGFmzAdmIAIkvZWlvYKdMg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=LKEL4ZvlAK8/qEal61MppuAWkWAdGw6yiLZmt1VJFpC0kZIQuqte0JpMTcakFDjTgxGDYrOmd7VHyFPooX5h/6y/MDskwWEsHcvYc0oqQIWdLTWWSMSmj2YPenOzy6gb65Vp9Q0z/SWXxgyH9n8y1nh0F1EIRPxP5IbEGSMbYE4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ZnGKWdc4; 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="ZnGKWdc4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 799B0C19421; Fri, 14 Nov 2025 17:11:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763140302; bh=KdPt1kVDnO95rsL6NNliJLGFmzAdmIAIkvZWlvYKdMg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ZnGKWdc4OQi1TdjZMUR3LD+7juKVZGWAyYe7+QViXFa622INTWRgLE2O2tKFoud9V 4/xbf0zjrd94xc1uXIcj2JcfJLYyr510GciQM0aRN2+l62sLj/IoA/ZUmjIz0T5J3B SiZ6ocVCyj6QF0H8wrF/kyCII1RA/CxSw32+JrUEbsbG6154KLapkjVZKkOpeMHI2m hYglF1n7c3oAjwTRpnzhB8cVs00W6orwNGzoaOj3bL272GRmBLVwmtPWC3RCxSdpBk z8yJipGkv0JrgzvsfE5pyda5kuDXq9ic8Jnb9ydHxK5wmMxwpS7cSZcbQNOvFsGGt6 4XUgQkdy6dzSQ== 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 07/13] kho: Remove global preserved_mem_map and store state in FDT In-Reply-To: <20251114155358.2884014-8-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 10:53:52 -0500") References: <20251114155358.2884014-1-pasha.tatashin@soleen.com> <20251114155358.2884014-8-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 18:11:39 +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 serialized memory map is tracked via > kho_out.preserved_mem_map and copied to the FDT during finalization. > This double tracking is redundant. > > Remove preserved_mem_map from kho_out. Instead, maintain the physical > address of the head chunk directly in the preserved-memory-map FDT > property. > > Introduce kho_update_memory_map() to manage this property. This function > handles: > 1. Retrieving and freeing any existing serialized map (handling the > abort/retry case). > 2. Updating the FDT property with the new chunk address. > > This establishes the FDT as the single source of truth for the handover > state. > > Signed-off-by: Pasha Tatashin Reviewed-by: Pratyush Yadav [...] -- Regards, Pratyush Yadav