Messages in this thread | | | Date | Tue, 26 Mar 2019 11:06:13 +0100 | Subject | Re: [PATCH 1/3] kexec: Do not map the kexec area as decrypted when SEV is active | From | Boris Petkov <> |
| |
On March 25, 2019 8:59:28 PM GMT+01:00, "Lendacky, Thomas" <Thomas.Lendacky@amd.com> wrote: >Maybe what would help is to describe why there is a difference between >SME >and SEV in regards to kexec. During a traditional boot under SME, SME >will >encrypt the kernel, so the SME kexec kernel also needs to be >un-encrypted >in order to replicate a normal SME boot. During a traditional boot >under >SEV, the kernel has already been loaded encrypted, so the SEV kexec >kernel >needs to be encrypted in order to replicate a normal SEV boot.
Yah, that should be in a comment above that function.
Thx.
-- Sent from a small device: formatting sux and brevity is inevitable.
| |