From: "Ashish Kalra" <ashish.kalra@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: devel@edk2.groups.io, brijesh.singh@amd.com, jejb@linux.ibm.com,
erdemaktas@google.com, jiewen.yao@intel.com, min.m.xu@intel.com,
lersek@redhat.com, jordan.l.justen@intel.com,
ard.biesheuvel@arm.com, dgilbert@redhat.com, pbonzini@redhat.com,
tobin@ibm.com, dovmurik@linux.ibm.com
Subject: Re: [PATCH v4 1/4] OvmfPkg/MemEncryptHypercallLib: add library to support SEV hypercalls.
Date: Wed, 23 Jun 2021 15:02:25 +0000 [thread overview]
Message-ID: <20210623150225.GA8080@ashkalra_ubuntu_server> (raw)
In-Reply-To: <20210623014747.GA6881@ashkalra_ubuntu_server>
Hello Tom, Brijesh,
Thanks for your comments and feedback on this patch-set.
With reference to those, i will remove the new library and
add the hypercall function inside BaseMemEncryptSevLib library.
Also i will let the hypercall handling for SEV-ES be done
as part of #VC exception handling in VmgExitLib library.
Thanks,
Ashish
On Wed, Jun 23, 2021 at 01:47:47AM +0000, Ashish Kalra wrote:
> Hello Tom,
>
> On Tue, Jun 22, 2021 at 05:47:48PM -0500, Tom Lendacky wrote:
> > On 6/21/21 8:56 AM, Ashish Kalra wrote:
> > > From: Ashish Kalra <ashish.kalra@amd.com>
> > >
> > > Add SEV and SEV-ES hypercall abstraction library to support SEV Page
> > > encryption/deceryption status hypercalls for SEV and SEV-ES guests.
> >
> > Does this have to be a new library? It's just a single function and so I
> > would think it could live in the BaseMemEncryptSevLib library where the
> > change to the c-bit is being done anyway.
> >
>
> Actually i like this approach, instead of adding a new library.
>
> Again, IIRC we had discussed this internally and then decided to
> create a new hypercall library similar to Xen, with reference to
> the email copied below :
>
> ...
> Xen has support under Ovmf for a Xen hypercall library
> (OvmfPkg/Library/XenHypercallLib). Take a look at that and maybe create
> something similar for KVM.
> ...
>
> Thanks,
> Ashish
next prev parent reply other threads:[~2021-06-23 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 13:56 [PATCH v4 0/4] SEV Live Migration support for OVMF Ashish Kalra
2021-06-21 13:56 ` [PATCH v4 1/4] OvmfPkg/MemEncryptHypercallLib: add library to support SEV hypercalls Ashish Kalra
2021-06-22 19:47 ` Brijesh Singh
2021-06-22 19:58 ` Brijesh Singh
2021-06-22 22:47 ` Lendacky, Thomas
2021-06-22 23:20 ` Ashish Kalra
2021-06-22 23:38 ` Brijesh Singh
2021-06-23 1:47 ` Ashish Kalra
2021-06-23 15:02 ` Ashish Kalra [this message]
2021-06-21 13:57 ` [PATCH v4 2/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall Ashish Kalra
2021-06-22 22:50 ` Lendacky, Thomas
2021-06-21 13:57 ` [PATCH v4 3/4] OvmfPkg/PlatformPei: Mark SEC GHCB page as unencrypted via hypercall Ashish Kalra
2021-06-22 20:35 ` Brijesh Singh
2021-06-21 13:57 ` [PATCH v4 4/4] OvmfPkg/PlatformDxe: Add support for SEV live migration Ashish Kalra
2021-06-22 23:06 ` Lendacky, Thomas
2021-06-24 16:29 ` Ashish Kalra
2021-06-22 17:20 ` [PATCH v4 0/4] SEV Live Migration support for OVMF Laszlo Ersek
2021-06-22 17:45 ` Brijesh Singh
2021-06-22 17:46 ` Ashish Kalra
2021-06-23 13:18 ` [edk2-devel] " Dov Murik
2021-06-23 16:42 ` Laszlo Ersek
2021-06-23 16:49 ` Laszlo Ersek
2021-06-23 17:03 ` Ashish Kalra
2021-06-30 9:11 ` Ashish Kalra
2021-06-30 16:25 ` [edk2-devel] " 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=20210623150225.GA8080@ashkalra_ubuntu_server \
--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