From: Sagi Shahar <sagis@google.com>
To: kai.huang@intel.com
Cc: bp@alien8.de, dave.hansen@intel.com, hpa@zytor.com,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@redhat.com, pbonzini@redhat.com,
peterz@infradead.org, seanjc@google.com, tglx@linutronix.de,
thomas.lendacky@amd.com, x86@kernel.org
Subject: [PATCH v5 0/5] TDX host: kexec() support
Date: Mon, 19 Aug 2024 14:21:56 -0700 [thread overview]
Message-ID: <20240819212156.166703-1-sagis@google.com> (raw)
In-Reply-To: <cover.1723723470.git.kai.huang@intel.com>
> Currently kexec() support and TDX host are muturally exclusive in the
> Kconfig. This series adds the TDX host kexec support so that they can
> work together and can be enabled at the same time in the Kconfig.
I tried testing the kexec functionality and noticed that the TDX module
fails initialization on the second kernel so you can't actually kexec
between 2 kernels that enable TDX. Is that the expected behavior? Are
there future patches to enable that functionality?
next prev parent reply other threads:[~2024-08-19 21:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 12:29 [PATCH v5 0/5] TDX host: kexec() support Kai Huang
2024-08-15 12:29 ` [PATCH v5 1/5] x86/kexec: do unconditional WBINVD for bare-metal in stop_this_cpu() Kai Huang
2024-08-15 12:29 ` [PATCH v5 2/5] x86/kexec: do unconditional WBINVD for bare-metal in relocate_kernel() Kai Huang
2024-08-15 23:45 ` Huang, Kai
2024-09-04 15:30 ` Borislav Petkov
2024-09-04 23:55 ` Huang, Kai
2024-08-15 12:29 ` [PATCH v5 3/5] x86/virt/tdx: Make module initializatiton state immutable in reboot notifier Kai Huang
2024-08-15 12:29 ` [PATCH v5 4/5] x86/kexec: Reset TDX private memory on platforms with TDX erratum Kai Huang
2024-08-15 12:29 ` [PATCH v5 5/5] x86/virt/tdx: Remove the !KEXEC_CORE dependency Kai Huang
2024-08-19 21:21 ` Sagi Shahar [this message]
2024-08-19 22:16 ` [PATCH v5 0/5] TDX host: kexec() support Huang, Kai
2024-08-19 22:28 ` Sagi Shahar
2024-08-19 22:43 ` Huang, Kai
2024-08-23 16:15 ` Sagi Shahar
2024-08-24 9:31 ` Huang, Kai
2024-08-26 19:22 ` Sagi Shahar
2024-08-26 22:50 ` Huang, Kai
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=20240819212156.166703-1-sagis@google.com \
--to=sagis@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--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