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 48F4E33436D for ; Fri, 14 Nov 2025 16:32:04 +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=1763137925; cv=none; b=RH2iIV/2uUEKJaoWhzRwqfunICazHZO7kSLjUN6NnAnlqR3m/oL9ivQ9f20WfaRZ29wPLezXdmCvIZOJNHAfMSMei35BOP4hszNVMyb1+onv72b37S6BN1HTX9O8bhaP0TEd7TqzzzOcwHxP40YNuGGOiQMIbzXubj8qoL6IF20= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763137925; c=relaxed/simple; bh=tvaWCesSZPV5aZlyiiBehWbeYK80FC2R6bxRgb0JBv8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=O5AYK8ZRYdLLDM8BILzf6TyoRFvVRkPjpQoXy9axTfZXlRx/3HDJf159ap/dsTF7KkELXFZSavgVFxgXlcYcEYoGScdf/vpTP4tfGppWxK4Dsq4xxBIXsliNIjprYB0XAgfG87lhpSbe+aIkRclQ1DdsK3q9NOm9WpZ9oKakcGE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=qCIGg/d2; 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="qCIGg/d2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7B467C4CEF8; Fri, 14 Nov 2025 16:32:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763137924; bh=tvaWCesSZPV5aZlyiiBehWbeYK80FC2R6bxRgb0JBv8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=qCIGg/d2HL42aDcB/Jy4naeEgwsC7p8QScxs+SzfBo8xshO5b0sREvxff35GjiixX G4OEItKvJLztO3DAFZBDxm6nSenW1ZsDeVLHeDmKkeY++3qj4Lr6UsH7jrFdyYqoua u91wQUy8WeigCtehOpi8RkYv20uysrmjxDNlBQ8eB2OYJqw1WSCNYIdHV4ZhINprVD kuwwxUsyP3u9Sp3Et/cKunlR1A4e/3rWao+LqVNt4FkFKmJX7Eh850SY9Ys+18ndCq uGVoMv2oJTSEiT1EpT30n9fXoF0iDd2SwTLhHlPOTBp5Kd11lJ4vQpVBv8Hk4ytYii v36JV88qUa68w== 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 01/13] kho: Fix misleading log message in kho_populate() In-Reply-To: <20251114155358.2884014-2-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 14 Nov 2025 10:53:46 -0500") References: <20251114155358.2884014-1-pasha.tatashin@soleen.com> <20251114155358.2884014-2-pasha.tatashin@soleen.com> Date: Fri, 14 Nov 2025 17:32:01 +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: > The log message in kho_populate() currently states "Will skip init for > some devices". This implies that Kexec Handover always involves > skipping device initialization. > > However, KHO is a generic mechanism used to preserve kernel memory across > reboot for various purposes, such as memfd, telemetry, or reserve_mem. > Skipping device initialization is a specific property of live update > drivers using KHO, not a property of the mechanism itself. > > Remove the misleading suffix to accurately reflect the generic nature of > KHO discovery. > > Signed-off-by: Pasha Tatashin Reviewed-by: Pratyush Yadav [...] -- Regards, Pratyush Yadav