From nobody Mon Oct 6 20:43:12 2025 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) (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 0CB6323ABB7; Thu, 17 Jul 2025 21:47:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.12 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752788866; cv=none; b=NZ/cviAzuWTMosA9EnQrxoOk+9jCygGS1cjfJMhM072Dksj95jZp0zElJthzRxklDpcnZrihMmTgjdZ3XdJ/oaZfeM7fAJtQ1Ut3dP8o8tuKH95nS7GchrsYWQTU7swKxO6Qdb+btHceZifmw/GuBw6dkLM8dm1pTRqJu6eG8q8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752788866; c=relaxed/simple; bh=iID5cAJ3gejVQfUBkOkcDPFzJBR7o+u/NSn8c6CW5tM=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=rm8ZHUT3p4xiF7E5THe3PeF9IHjw1cCKlCkvaGEVESiOLjrRVTe5Tuhv8quZsXC0IwkjIbfP6BY2mUdP/P53HBUX9DWVn8BbZGdSjcSMreO5hV6lB0z1/LaXM3D0PeeXg7WBeyjJfBHX1irl1AOPmDjkKBaz6nLHRyMyAWFcpyU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=Wz7gyZep; arc=none smtp.client-ip=198.175.65.12 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="Wz7gyZep" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1752788865; x=1784324865; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=iID5cAJ3gejVQfUBkOkcDPFzJBR7o+u/NSn8c6CW5tM=; b=Wz7gyZepRPZG0Nj6xHqDG+Nemsp6QoUP+XDH2i/Bk1hOXA0LDKUkusdt Wuz2wuwwbphP4Zaelw7CsEhIytrVP6Lwm8pLrS8JGmCx2t7Hr5Yg6AF1/ wwY0etRPo+M4fzxFklKQEmzZw6UlVPaw5JIjl8oGozWAqGZ8/kqY0fypK N58YaDzlt4o2AigBxrQH2DntKtlXhFadgtzSUzxNZy84oGfYqfX/Y9YbQ eyA7IgCXT/bak79N0AB6XWv61BFL8Na5jIx8N/+QJdujBRFe93MNSZ4Iw 9Ja/QcM9p3FuhAQs2QPXdW/nQWvelbvraxmCe8M87HsZxn8h64E62jbuK w==; X-CSE-ConnectionGUID: oUHehmVeTTyni9N+QtE2EA== X-CSE-MsgGUID: gSy5iMXhTrOtgeT3In14Mw== X-IronPort-AV: E=McAfee;i="6800,10657,11495"; a="66527839" X-IronPort-AV: E=Sophos;i="6.16,319,1744095600"; d="scan'208";a="66527839" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jul 2025 14:47:45 -0700 X-CSE-ConnectionGUID: p8TulCapT4CRonOdwwXPSg== X-CSE-MsgGUID: UpNwiVMmTJKxZbOJgmVZTQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,319,1744095600"; d="scan'208";a="157295552" Received: from vverma7-mobl3.amr.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.124.221.39]) by orviesa010-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jul 2025 14:47:39 -0700 From: Kai Huang To: dave.hansen@intel.com, bp@alien8.de, tglx@linutronix.de, peterz@infradead.org, mingo@redhat.com, hpa@zytor.com, thomas.lendacky@amd.com Cc: x86@kernel.org, kas@kernel.org, rick.p.edgecombe@intel.com, dwmw@amazon.co.uk, linux-kernel@vger.kernel.org, pbonzini@redhat.com, seanjc@google.com, kvm@vger.kernel.org, reinette.chatre@intel.com, isaku.yamahata@intel.com, dan.j.williams@intel.com, ashish.kalra@amd.com, nik.borisov@suse.com, chao.gao@intel.com, sagis@google.com, Farrah Chen Subject: [PATCH v4 6/7] x86/virt/tdx: Update the kexec section in the TDX documentation Date: Fri, 18 Jul 2025 09:46:43 +1200 Message-ID: X-Mailer: git-send-email 2.50.1 In-Reply-To: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" TDX host kernel now supports kexec/kdump. Update the documentation to reflect that. Opportunistically, remove the parentheses in "Kexec()" and move this section under the "Erratum" section because the updated "Kexec" section now refers to that erratum. Signed-off-by: Kai Huang Tested-by: Farrah Chen Reviewed-by: Rick Edgecombe --- Documentation/arch/x86/tdx.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Documentation/arch/x86/tdx.rst b/Documentation/arch/x86/tdx.rst index 719043cd8b46..61670e7df2f7 100644 --- a/Documentation/arch/x86/tdx.rst +++ b/Documentation/arch/x86/tdx.rst @@ -142,13 +142,6 @@ but depends on the BIOS to behave correctly. Note TDX works with CPU logical online/offline, thus the kernel still allows to offline logical CPU and online it again. =20 -Kexec() -~~~~~~~ - -TDX host support currently lacks the ability to handle kexec. For -simplicity only one of them can be enabled in the Kconfig. This will be -fixed in the future. - Erratum ~~~~~~~ =20 @@ -171,6 +164,13 @@ If the platform has such erratum, the kernel prints ad= ditional message in machine check handler to tell user the machine check may be caused by kernel bug on TDX private memory. =20 +Kexec +~~~~~~~ + +Currently kexec doesn't work on the TDX platforms with the aforementioned +erratum. It fails when loading the kexec kernel image. Otherwise it +works normally. + Interaction vs S3 and deeper states ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =20 --=20 2.50.0