From: Dave Hansen <dave.hansen@intel.com>
To: Kai Huang <kai.huang@intel.com>,
bp@alien8.de, tglx@linutronix.de, peterz@infradead.org,
mingo@redhat.com
Cc: kirill.shutemov@linux.intel.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
seanjc@google.com, rick.p.edgecombe@intel.com,
reinette.chatre@intel.com, isaku.yamahata@intel.com,
dan.j.williams@intel.com, thomas.lendacky@amd.com,
ashish.kalra@amd.com, nik.borisov@suse.com, sagis@google.com
Subject: Re: [PATCH] x86/virt/tdx: Make TDX and kexec mutually exclusive at runtime
Date: Thu, 17 Apr 2025 10:50:06 -0700 [thread overview]
Message-ID: <7bd03311-0c4c-41e6-b6dc-803b6455f170@intel.com> (raw)
In-Reply-To: <20250416230259.97989-1-kai.huang@intel.com>
On 4/16/25 16:02, Kai Huang wrote:
> Full support for kexec on a TDX host would require complex work.
> The cache flushing required would need to happen while stopping
> remote CPUs, which would require changes to a fragile area of the
> kernel.
Doesn't kexec already stop remote CPUs? Doesn't this boil down to a
WBINVD? How is that complex?
> It would also require resetting TDX private pages, which is non-
> trivial since the core kernel does not track them.
Why? The next kernel will just use KeyID-0 which will blast the old
pages away with no side effects... right?
> Lastly, it would have to rely on a yet-to-be documented behavior
> around the TME key (KeyID 0).
I'll happily wait for the documentation if you insist on it (I don't).
next prev parent reply other threads:[~2025-04-17 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 23:02 Kai Huang
2025-04-17 17:07 ` Edgecombe, Rick P
2025-04-17 17:50 ` Dave Hansen [this message]
2025-04-17 18:21 ` Edgecombe, Rick P
2025-04-17 18:56 ` Dave Hansen
2025-04-22 4:10 ` Huang, Kai
2025-05-07 21:03 ` Edgecombe, Rick P
2025-05-07 23:49 ` Edgecombe, Rick P
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=7bd03311-0c4c-41e6-b6dc-803b6455f170@intel.com \
--to=dave.hansen@intel.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--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=rick.p.edgecombe@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®