From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Huang, Kai" <kai.huang@intel.com>, "bp@alien8.de" <bp@alien8.de>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>
Cc: "nik.borisov@suse.com" <nik.borisov@suse.com>,
"bhe@redhat.com" <bhe@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"x86@kernel.org" <x86@kernel.org>,
"sagis@google.com" <sagis@google.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"ashish.kalra@amd.com" <ashish.kalra@amd.com>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>
Subject: Re: [RFC PATCH 3/5] x86/kexec: Disable kexec/kdump on platforms with TDX partial write erratum
Date: Wed, 12 Mar 2025 23:27:00 +0000 [thread overview]
Message-ID: <4ac689506269e907774806a484e15171b04ffc63.camel@intel.com> (raw)
In-Reply-To: <408103f145360dfa04a41bc836ca2c724f29deb0.1741778537.git.kai.huang@intel.com>
On Thu, 2025-03-13 at 00:34 +1300, Kai Huang wrote:
> The impact to userspace is the users will get an error when loading the
> kexec/kdump kernel image:
>
> kexec_load failed: Operation not supported
>
> This might be confusing to the users, thus also print the reason in the
> dmesg:
>
> [..] kexec: not allowed on platform with tdx_pw_mce bug.
Continuing an internal discussion... A problem with the plan to more simply
start support for kexec by not supporting the errata platforms is that when
these platforms configure TDX they will lose kexec by default.
Probably a better default for a lot of kernels would be to have kexec work by
default, and require opt-in to use TDX (and lose kexec). One idea was a kernel
parameter be required to enable TDX on those platforms. But then we are starting
to add complexity to avoid other complexity (the errata platform kexec support).
Still, it may be a net win on complexity.
next prev parent reply other threads:[~2025-03-12 23:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 11:34 [RFC PATCH 0/5] TDX host: kexec/kdump support Kai Huang
2025-03-12 11:34 ` [RFC PATCH 1/5] x86/kexec: Do unconditional WBINVD for bare-metal in stop_this_cpu() Kai Huang
2025-03-13 18:40 ` Edgecombe, Rick P
2025-03-14 10:03 ` Huang, Kai
2025-03-14 15:11 ` Tom Lendacky
2025-03-14 16:28 ` Edgecombe, Rick P
2025-03-14 18:18 ` Tom Lendacky
2025-03-14 18:57 ` Edgecombe, Rick P
2025-03-17 10:11 ` Huang, Kai
2025-03-18 3:41 ` Edgecombe, Rick P
2025-03-20 0:03 ` Huang, Kai
2025-03-17 12:52 ` kirill.shutemov
2025-03-17 21:59 ` Edgecombe, Rick P
2025-03-19 16:41 ` Dave Hansen
2025-03-19 17:03 ` Edgecombe, Rick P
2025-03-19 21:42 ` Huang, Kai
2025-03-12 11:34 ` [RFC PATCH 2/5] x86/kexec: Do unconditional WBINVD for bare-metal in relocate_kernel() Kai Huang
2025-03-13 23:17 ` Edgecombe, Rick P
2025-03-14 9:44 ` Huang, Kai
2025-03-18 3:54 ` Edgecombe, Rick P
2025-03-19 9:57 ` Huang, Kai
2025-03-19 16:20 ` Edgecombe, Rick P
2025-03-12 11:34 ` [RFC PATCH 3/5] x86/kexec: Disable kexec/kdump on platforms with TDX partial write erratum Kai Huang
2025-03-12 23:27 ` Edgecombe, Rick P [this message]
2025-03-13 0:57 ` Huang, Kai
2025-03-13 17:18 ` Edgecombe, Rick P
2025-03-13 22:32 ` Huang, Kai
2025-03-13 22:47 ` Edgecombe, Rick P
2025-03-13 23:57 ` Huang, Kai
2025-03-14 19:03 ` Edgecombe, Rick P
2025-03-17 1:19 ` Huang, Kai
2025-03-17 23:53 ` Edgecombe, Rick P
2025-03-12 11:34 ` [RFC PATCH 4/5] x86/virt/tdx: Remove the !KEXEC_CORE dependency Kai Huang
2025-03-12 11:34 ` [RFC PATCH 5/5] x86/virt/tdx: Update the kexec section in the TDX documentation Kai Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ac689506269e907774806a484e15171b04ffc63.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=ashish.kalra@amd.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=sagis@google.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®