From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ashish.kalra@amd.com
Cc: dovmurik@linux.vnet.ibm.com, brijesh.singh@amd.com,
tobin@ibm.com, Jon.Grimm@amd.com, Thomas.Lendacky@amd.com,
jejb@linux.ibm.com, frankeh@us.ibm.com, dgilbert@redhat.com,
jordan.l.justen@intel.com, ard.biesheuvel@arm.com
Subject: Re: [edk2-devel] [PATCH v3 0/3] SEV Page Encryption Bitmap support for OVMF.
Date: Tue, 8 Dec 2020 03:44:45 +0100 [thread overview]
Message-ID: <d199c7bb-4987-c979-5fb0-0a15bb305fec@redhat.com> (raw)
In-Reply-To: <20201204081009.GA767@ashkalra_ubuntu_server>
On 12/04/20 09:10, Ashish Kalra wrote:
> On Fri, Dec 04, 2020 at 04:50:05AM +0100, Laszlo Ersek wrote:
>> On 12/04/20 01:03, Ashish Kalra wrote:
>>> From: Ashish Kalra <ashish.kalra@amd.com>
>>>
>>> By default all the SEV guest memory regions are considered encrypted,
>>> if a guest changes the encryption attribute of the page (e.g mark a
>>> page as decrypted) then notify hypervisor. Hypervisor will need to
>>> track the unencrypted pages. The information will be used during
>>> guest live migration, guest page migration and guest debugging.
>>>
>>> The patch-set also adds a new SEV and SEV-ES hypercall abstraction
>>> library to support SEV Page encryption/decryption status hypercalls
>>> for SEV and SEV-ES guests.
>>>
>>> BaseMemEncryptSevLib invokes hypercalls via this new hypercall library.
>>>
>>> A branch containing these patches is available here:
>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fashkalra%2Fedk2%2Ftree%2Fsev_page_encryption_bitmap_v3&data=04%7C01%7Cashish.kalra%40amd.com%7Cbc3c88f21f1d40b322b408d89807b5c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637426506192800828%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VZzP2MVJSECgMhOyuCCASw58g74BiCVAH9JW8hZG3Tw%3D&reserved=0
>>>
>>> Changes since v2:
>>> - GHCB_BASE setup during reset-vector as decrypted is marked explicitly
>>> in the hypervisor page encryption bitmap after setting the
>>> PcdSevEsIsEnabled PCD.
>>>
>>> Changes since v1:
>>> - Mark GHCB_BASE setup during reset-vector as decrypted explicitly in
>>> the hypervisor page encryption bitmap.
>>> - Resending the series with correct shallow threading.
>>>
>>> Ashish Kalra (2):
>>> OvmfPkg/MemEncryptHypercallLib: add library to support SEV hypercalls.
>>> OvmfPkg/PlatformPei: Mark SEC GHCB page in the page encrpytion bitmap.
>>>
>>> Brijesh Singh (1):
>>> OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall
>>>
>>> .../Include/Library/MemEncryptHypercallLib.h | 37 ++++++
>>> .../BaseMemEncryptSevLib.inf | 1 +
>>> .../BaseMemEncryptSevLib/X64/VirtualMemory.c | 18 +++
>>> .../MemEncryptHypercallLib.c | 105 ++++++++++++++++++
>>> .../MemEncryptHypercallLib.inf | 39 +++++++
>>> .../X64/AsmHelperStub.nasm | 39 +++++++
>>> OvmfPkg/OvmfPkgX64.dsc | 1 +
>>> OvmfPkg/PlatformPei/AmdSev.c | 10 ++
>>> 8 files changed, 250 insertions(+)
>>> create mode 100644 OvmfPkg/Include/Library/MemEncryptHypercallLib.h
>>> create mode 100644 OvmfPkg/Library/MemEncryptHypercallLib/MemEncryptHypercallLib.c
>>> create mode 100644 OvmfPkg/Library/MemEncryptHypercallLib/MemEncryptHypercallLib.inf
>>> create mode 100644 OvmfPkg/Library/MemEncryptHypercallLib/X64/AsmHelperStub.nasm
>>>
>>
>> I'll need some time to get to this series.
>>
>> I'm fairly certain though, from a quick skim, that this series breaks
>> all DSC files under OvmfPkg except X64. Please fix that.
>>
>>
>
> Ok thanks Laszlo, i will fix this.
Thanks.
I can see a new comment for the series from Dov Murik, and I think
that's awesome. I'd welcome if there were lively exchanges around OVMF
patch sets. I'm selfish of course: I'd like to delegate reviews.
So, on this patch set, I notice it does not add the new
(MemEncryptHypercallLib-related) files to Maintainers.txt, namely
section "OvmfPkg: SEV-related modules".
Please include such a patch in v4 -- if Tom and Brijesh agree, I'd like
to put the new lib explicitly under their reviewership.
Also, I plan to review this series (v4, at this point) only for
formalities. I'd like to receive an R-b from Tom or Brijesh [*], and
another from Dov or a colleague at IBM, for this series; those together
should suffice for merging the library.
[*] Brijesh seems to be the original author of patch#2, so maybe Tom is
a better-poised reviewer for this.
Thanks
Laszlo
next prev parent reply other threads:[~2020-12-08 2:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 0:03 [PATCH v3 0/3] SEV Page Encryption Bitmap support for OVMF Ashish Kalra
2020-12-04 0:03 ` [PATCH v3 1/3] OvmfPkg/MemEncryptHypercallLib: add library to support SEV hypercalls Ashish Kalra
2020-12-06 12:43 ` Dov Murik
2020-12-08 14:23 ` Ashish Kalra
2020-12-04 0:03 ` [PATCH v3 2/3] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall Ashish Kalra
2020-12-04 0:03 ` [PATCH v3 3/3] OvmfPkg/PlatformPei: Mark SEC GHCB page in the page encrpytion bitmap Ashish Kalra
2020-12-04 3:50 ` [edk2-devel] [PATCH v3 0/3] SEV Page Encryption Bitmap support for OVMF Laszlo Ersek
2020-12-04 8:10 ` Ashish Kalra
2020-12-08 2:44 ` Laszlo Ersek [this message]
2020-12-08 4:44 ` Brijesh Singh
2020-12-08 14:57 ` Lendacky, Thomas
2020-12-10 7:53 ` Laszlo Ersek
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-list 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=d199c7bb-4987-c979-5fb0-0a15bb305fec@redhat.com \
--to=devel@edk2.groups.io \
/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