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 9A2D432F748 for ; Mon, 11 May 2026 11:00: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=1778497224; cv=none; b=sew4H55VmEPV7qAVrFW2B9ZtiyOJWlTkwLdgp2wB51beKVDdDt8a23S/A8GGu18ybZoht4svNtux7RoGTK6l2+2ry2mWe4m0ZY66nKsu+Xl2mLtS8MVq8g1SHWIw6IRHWofiH6CSioRjB0pjZXojPec3T1PIMYXFDP35YqZjra8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778497224; c=relaxed/simple; bh=izvnagj9ZLJVxR+qNc7RMbvt9I2ey8INGl6X8JOMJbo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=gSkKZtFeQoT6GTzFpDVWeEhjZ3qSsXITgrLZE8OCFaRCV90D8rXlzB1vbjYuDv3N8ogE6ByLhTcB/PhzCtT1RzkWi6k/l7PMci1WZ5NVlAjPB7anHB2Gfca6F7Jg1blmQ9PPxClG9gJRuYDMtw4XeI8V3ALQfSYMokneEldyI7M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=EKgSxuzD; 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="EKgSxuzD" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02967C2BCB0; Mon, 11 May 2026 11:00:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778497224; bh=izvnagj9ZLJVxR+qNc7RMbvt9I2ey8INGl6X8JOMJbo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=EKgSxuzDb6hj8qW6BihC8pNQpuLkpsS/rpx3FJpEScZc4OBPrfWt/ibmj9igKBasG SFrgdhQpEKGkgE7P+7isoCIrzDb6xjlhFz8R1QS5FGx062XzkqMqmmup+di9h16mCp m6IijHxemds9GdkcSbj8GdRq9Re49Al/h86jRNbdBqsGV7AhmqdJw8mr73Si8CFNAD I+MMOroM3IEeHiuzN7ErYkwMESlI79yRWU0TB6+/t7r1mHBjWHClN8I8OqKjMUEDda nniyDISCueVN8cpTW/129Lv+ty0uhEJDy3XcPqu/9eUwEUGPA3K7foSNF599cCajlV xOMnTylqpXrjA== From: Pratyush Yadav To: Pasha Tatashin Cc: rppt@kernel.org, sourabhjain@linux.ibm.com, jbouron@amazon.com, akpm@linux-foundation.org, linux-mm@kvack.org, bhe@redhat.com, linux-kernel@vger.kernel.org, dan.carpenter@linaro.org, rafael.j.wysocki@intel.com, piliu@redhat.com, kexec@lists.infradead.org, pratyush@kernel.org, graf@amazon.com, changyuanl@google.com, mario.limonciello@amd.com Subject: Re: [PATCH v2 1/3] kho: skip KHO data for context-preserving kexec In-Reply-To: <20260506182039.2623553-6-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Wed, 6 May 2026 14:20:41 -0400") References: <20260506182039.2623553-5-pasha.tatashin@soleen.com> <20260506182039.2623553-6-pasha.tatashin@soleen.com> Date: Mon, 11 May 2026 13:00:20 +0200 Message-ID: <2vxzzf26cit7.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 Wed, May 06 2026, Pasha Tatashin wrote: > A preserve_context kexec returns to the current kernel, which means the > 2nd kernel does not use KHO data (and their memory spaces don't > overlap). Passing KHO data to the 2nd kernel via setup_data or > devicetree is unnecessary. > > Add a check in kho_fill_kimage() and return early if preserve_context is > set, to avoid passing KHO state during context-preserving kexecs. > > Fixes: 3bdecc3c93f9 ("kexec: add KHO support to kexec file loads") > Signed-off-by: Pasha Tatashin Reviewed-by: Pratyush Yadav (Google) [...] -- Regards, Pratyush Yadav