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 322103A1E72 for ; Fri, 2 Jan 2026 20:23:24 +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=1767385405; cv=none; b=ro9v8ln8nWEA65nOusoTucTAejOwu3H6TPYee7EzekgEkywAgFZEhiSH83yJruqiQ0umdFFcDciltOhkGS63nz/vrio/WQ8iTorV6kodDruUGZnJGb5mNsncGYbGduD6qp/olVe0Bv99Nes8IMMaKuZhZ1EpvJbolPIEHpx/Rlg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767385405; c=relaxed/simple; bh=36h+gzQOCGURAdbtJyCuaVTakIb422pTXIoravRz/yA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=ggqpawnXWxlnTswqq59xHQzrWOdn7OVRYreGLdUHSKvm5esz5hB3S0eS5ECJob+V8hvg2Dk5Xa0F3VeQfMa6tEcTBSvrUOlGTHzLa8LEY6sB4L9OcMXGt6FCdzVL9JAZuKJcCOT0LdFue6iiUabFwkhgL8IlQa7RVhLj5vES8bk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=C850m0yz; 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="C850m0yz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5E5E1C116B1; Fri, 2 Jan 2026 20:23:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1767385404; bh=36h+gzQOCGURAdbtJyCuaVTakIb422pTXIoravRz/yA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=C850m0yzR3hfqz7dBIq6J71yU2NNbzw4mZaZTNyPS1TZV7qYNGtTDRPG8kpI1KJZU ofuE0e2/hKuY+6qQQ+lwQ0cj+QRkeNR26LRPa8WC2Y0oXilcU6aovdOyDqulr10/0J 5w+ird2Y68JVQc1u6tcW/DP7po+/gYn1EcUYwlJp6jHPGn2Yy/S+qSk+7FuXSSkyt5 nCJuLXK565YOlUy2SvzN3oX2xAQGgxxkic4YaKhFFok0GamRAPMXKe6yrSoNzIPeAe i1FlTFFmTkhtejMhNuCFQjPyckllVuKw4dtWQQ8M+NlfERKco0rQC6McmwA9iTE7T4 hcbWYVbQZ+9zw== From: Pratyush Yadav To: Breno Leitao Cc: Alexander Graf , Mike Rapoport , Pasha Tatashin , Pratyush Yadav , linux-kernel@vger.kernel.org, kexec@lists.infradead.org, linux-mm@kvack.org, usamaarif642@gmail.com, rmikey@meta.com, clm@fb.com, riel@surriel.com, kernel-team@meta.com Subject: Re: [PATCH v2 2/2] kexec: history: track kexec boot counter In-Reply-To: <20260102-kho-v2-2-1747b1a3a1d6@debian.org> (Breno Leitao's message of "Fri, 02 Jan 2026 06:53:24 -0800") References: <20260102-kho-v2-0-1747b1a3a1d6@debian.org> <20260102-kho-v2-2-1747b1a3a1d6@debian.org> Date: Fri, 02 Jan 2026 21:23:18 +0100 Message-ID: <86o6nb7oi1.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 On Fri, Jan 02 2026, Breno Leitao wrote: > Track and display the number of kexec boots since the last cold reboot Nit: this does not track kexec boots, it tracks KHO boots. None of this can work on normal kexec boots. Can you please update the wording to make that clear? > when CONFIG_KEXEC_HISTORY is enabled. > > This extends the previous kernel release tracking feature by adding > a counter that increments with each kexec boot. The counter provides > visibility into the kexec chain depth, which is useful for understanding > boot history in production environments. > > Add a new property, "kexec-count" in KHO FDT alongside the existing > "previous-release" property. The counter is: > > - Initialized to 0 when kho_in is instantiated. > - Incremented by 1 on each subsequent kexec. > - Printed alongside the previous kernel release version. > > The counter is stored as a 32-bit unsigned integer in FDT format and is > only active when CONFIG_KEXEC_HISTORY is enabled. We have such a counter for LUO as well from the properly "liveupdate-number". If you're using LUO, why can't you use that counter directly? If you're not using LUO, I'm curious, what's your use case? Right now KHO only supports reserve-mem outside of LUO. Is that what you plan to use? Also, do we want to keep both counters independently? Or do we have one and drop the other? Pasha, what do you think? [...] -- Regards, Pratyush Yadav