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 EB5B42DCBF3 for ; Fri, 14 Nov 2025 19:35:54 +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=1763148955; cv=none; b=ssMIkts9gqaNchmIjSmfbKKr4B7FQse07/tSk8KqXw4TPntAC9xw9cltrvh7UwyXwTalvwhdaRiZGltPtYVki3JHG/+5yAhT3tSX94YoFO4C2HpScPlLB88nstXLeCQny9NR8/VprpgcMbaFnRg8jOFAipqRGAQg6Q/MutE4C04= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763148955; c=relaxed/simple; bh=Q1O4BIVR1FCS7fU5WDAS+HptHA2cmt8TA5K3Q3jWw3Q=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=sCZ7tVykV61cPWdN+/8JLnmNDr2X72DOKuXBI/+nJZmsi2FikykD8xX+TbBgoXh7qRSMecJnztOcygLFbLBJPaQd31J4OlI1awI/hr6OgOXX5hC6FLZXMB/1kXt6LiBP3T8WrVgd3XNoeRY7Czb+A3TKdZmB7BCjA4ZbWXbzrtM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Dj5HqMWk; 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="Dj5HqMWk" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4A4BCC19421; Fri, 14 Nov 2025 19:35:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763148954; bh=Q1O4BIVR1FCS7fU5WDAS+HptHA2cmt8TA5K3Q3jWw3Q=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Dj5HqMWkFNbuohcjbv4dicuiDeZh9VXlrv4Nq8qQeqKJfLexZPY2HiN/CaXHOqLbs xsPClbHS3mTj0znKO+cynJD/nzJ1g3VtC1sRbQ5BZg8keXFC6PTtm07C9PEfRwfgID 9eQrI9Lgcfl4RcBrYMTj5Gxf8uCMx2ARWuSmLOp8indblWHrJwTNgBuho0KBn+0PHu +yVFF9a1HKePZGlxXLWtqBRbi5qco9Y3hFVgdIMcgnLFjI38tialKDlHkQ8ynjQMux grCYboOy1/R63jsDHZkcqmVY0m1TeO4Xvov+J/If6GUxuOUgBxayskyv16HXgznSbP Y3uYfZM3JAT2g== 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 v2 13/13] kho: Add Kconfig option to enable KHO by default In-Reply-To: <20251114190002.3311679-14-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 14:00:02 -0500") References: <20251114190002.3311679-1-pasha.tatashin@soleen.com> <20251114190002.3311679-14-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 20:35:51 +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, Kexec Handover must be explicitly enabled via the kernel > command line parameter `kho=on`. > > For workloads that rely on KHO as a foundational requirement (such as > the upcoming Live Update Orchestrator), requiring an explicit boot > parameter adds redundant configuration steps. > > Introduce CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT. When selected, KHO > defaults to enabled. This is equivalent to passing kho=on at boot. > The behavior can still be disabled at runtime by passing kho=off. > > Signed-off-by: Pasha Tatashin > Reviewed-by: Mike Rapoport (Microsoft) Reviewed-by: Pratyush Yadav [...] -- Regards, Pratyush Yadav