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 CD6F1338912 for ; Fri, 14 Nov 2025 17:34:13 +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=1763141653; cv=none; b=BKMPk1ISYn4wP6E2Qg55Pok88n7/EmOUhrR+iqdHTruDZuQWtMIyytEaN8CWcIUgwpjeENwLa7yP1FrE9pgWWOW23Ux2oCA8FJDW+h4hZ3VBS1oGlay8uWs5blo6vX3ihA70kFrEKStcKC/C34GtyeMMXMa6+aLY3aeQ3xGKbC0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763141653; c=relaxed/simple; bh=sfUecj5LXq8ygB5hZwBv17W6tTJhiXt4mvVHfCkRIYo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=f/HZvDEsApq+D54V2HWehL5GmNSHLB9vxsjTngNpiY2VU9iqy2xrfPpuUHVSI++2fXsa759XzHZYK3TGYlVyt+UQygOUEjRBTWXYYlqXSIGZjSBnxgytne7ITmLOXFchQgedz79efOfLe5KbWNUfnaJzSbbHadXyDeoqsKa0tK0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=pFcxALcK; 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="pFcxALcK" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 22048C116B1; Fri, 14 Nov 2025 17:34:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763141653; bh=sfUecj5LXq8ygB5hZwBv17W6tTJhiXt4mvVHfCkRIYo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pFcxALcKxbGfPOXU6jl11AI5j70DY3GzkB3VavJQ8ZlP+ZbFdyUw2vNOqThHcLzu/ /GPFvJl0xWEhLxkz8YVAOvYkrqK/Rn6YyCse+wrvOL4DujdiBGxmMDpfo6SnAN4wwb etVVvPYOAwkB4w0QvDSsFTPw7Re5IRsadi1m3UhYANYlNtuVSxOM80ku9tGoddJJOh I398yJQxGOzIMpgjO2wvkROaHfZpvJMRGixyeTM4CqdXoLIay3J5s1Gd3qCfke/lcn TRxhlF7eZ1xXJRLlMXYfy21PY0gFifnNLCfFt/1UN8D2auos2yinyUH7wZAUzu9N9H wljpJKETg73Cg== 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 12/13] kho: Add Kconfig option to enable KHO by default In-Reply-To: <20251114155358.2884014-13-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 10:53:57 -0500") References: <20251114155358.2884014-1-pasha.tatashin@soleen.com> <20251114155358.2884014-13-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 18:34:09 +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: Pratyush Yadav [...] -- Regards, Pratyush Yadav