From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>
Cc: Borislav Petkov <bp@alien8.de>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Isaku Yamahata <isaku.yamahata@intel.com>,
x86@kernel.org, linux-coco@lists.linux.dev,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Kexec enabling in TDX guest
Date: Fri, 24 Feb 2023 07:22:18 -0800 [thread overview]
Message-ID: <f32f1f77-c707-ae19-ae1a-dc0a37fa9806@intel.com> (raw)
In-Reply-To: <20230224143004.xqhpv6upn2fkqkjp@box.shutemov.name>
On 2/24/23 06:30, Kirill A. Shutemov wrote:
> Ideally, it has to be addressed on BIOS level: it has to provide a way to
> offline CPUs, putting it back to pre-wakeup state.
Is there anything stopping us from just parking the CPUs in a loop
looking at 'acpi_mp_wake_mailbox_paddr'? Basically park them in a way
which is indistinguishable from what the BIOS did.
next prev parent reply other threads:[~2023-02-24 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 23:48 [PATCH 0/2] Kexec enabling in TDX guest Kirill A. Shutemov
2023-02-13 23:48 ` [PATCH 1/2] x86/kexec: Preserve CR4.MCE during kexec Kirill A. Shutemov
2023-02-16 1:49 ` Edgecombe, Rick P
2023-02-16 9:43 ` Kirill A. Shutemov
2023-02-16 17:33 ` Edgecombe, Rick P
2023-02-16 19:46 ` Andrew Cooper
2023-02-13 23:48 ` [PATCH 2/2] x86/tdx: Convert shared memory back to private on kexec Kirill A. Shutemov
2023-02-15 1:53 ` Huang, Kai
2023-02-16 17:50 ` [PATCH 0/2] Kexec enabling in TDX guest Dave Hansen
2023-02-16 18:12 ` Kirill A. Shutemov
2023-02-16 18:32 ` Dave Hansen
2023-02-22 10:26 ` David Woodhouse
2023-02-24 14:30 ` Kirill A. Shutemov
2023-02-24 15:22 ` Dave Hansen [this message]
2023-02-24 16:12 ` Kirill A. Shutemov
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=f32f1f77-c707-ae19-ae1a-dc0a37fa9806@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dwmw2@infradead.org \
--cc=isaku.yamahata@intel.com \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).