From: Tom Lendacky <thomas.lendacky@amd.com>
To: Vasant Karasulli <vkarasulli@suse.de>
Cc: Vasant k <vsntk18@gmail.com>,
x86@kernel.org, joro@8bytes.org, cfir@google.com,
dan.j.williams@intel.com, dave.hansen@linux.intel.com,
ebiederm@xmission.com, erdemaktas@google.com, hpa@zytor.com,
jgross@suse.com, jslaby@suse.cz, keescook@chromium.org,
kexec@lists.infradead.org, kvm@vger.kernel.org,
linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org,
luto@kernel.org, martin.b.radev@gmail.com, mhiramat@kernel.org,
mstunes@vmware.com, nivedita@alum.mit.edu, peterz@infradead.org,
rientjes@google.com, seanjc@google.com, stable@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v4 0/9] x86/sev: KEXEC/KDUMP support for SEV-ES guests
Date: Tue, 12 Mar 2024 11:13:54 -0500 [thread overview]
Message-ID: <a82d24f8-d185-47a7-91df-4706658843e5@amd.com> (raw)
In-Reply-To: <ZfBx2ewmB06qQajs@vasant-suse>
On 3/12/24 10:16, Vasant Karasulli wrote:
> On Di 12-03-24 09:04:13, Tom Lendacky wrote:
>> On 3/11/24 15:32, Vasant k wrote:
>>> Hi Tom,
>>>
>>> Right, it just escaped my mind that the SNP uses the secrets page
>>> to hand over APs to the next stage. I will correct that in the next
>>
>> Not quite... The MADT table lists the APs and the GHCB AP Create NAE event
>> is used to start the APs.
>
> Alright. So AP Jump Table is not used like in the case of SEV-ES. Thanks,
Right. It can be, but we don't use that method in Linux.
Thanks,
Tom
> I will keep the changes in the patch set exclusively for SEV-ES then.
>
> - Vasant
prev parent reply other threads:[~2024-03-12 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 16:17 [PATCH v4 0/9] x86/sev: KEXEC/KDUMP support for SEV-ES guests Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 1/9] x86/kexec/64: Disable kexec when SEV-ES is active Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 2/9] x86/sev: Save and print negotiated GHCB protocol version Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 3/9] x86/sev: Set GHCB data structure version Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 4/9] x86/sev: Setup code to park APs in the AP Jump Table Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 5/9] x86/sev: Park APs on AP Jump Table with GHCB protocol version 2 Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 6/9] x86/sev: Use AP Jump Table blob to stop CPU Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 7/9] x86/sev: Add MMIO handling support to boot/compressed/ code Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 8/9] x86/sev: Handle CLFLUSH MMIO events Vasant Karasulli
2024-03-11 16:17 ` [PATCH v4 9/9] x86/kexec/64: Support kexec under SEV-ES with AP Jump Table Blob Vasant Karasulli
2024-03-11 19:19 ` [PATCH v4 0/9] x86/sev: KEXEC/KDUMP support for SEV-ES guests Tom Lendacky
[not found] ` <CAF2zH5qZKEmECy=9vG4sLmdDt5k7nC=MwjKvJLyVfPyFzt+0hA@mail.gmail.com>
2024-03-12 14:04 ` Tom Lendacky
2024-03-12 15:16 ` Vasant Karasulli
2024-03-12 16:13 ` Tom Lendacky [this message]
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=a82d24f8-d185-47a7-91df-4706658843e5@amd.com \
--to=thomas.lendacky@amd.com \
--cc=cfir@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=erdemaktas@google.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=martin.b.radev@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mstunes@vmware.com \
--cc=nivedita@alum.mit.edu \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=vkarasulli@suse.de \
--cc=vsntk18@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).