From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: devel@edk2.groups.io, James Bottomley <jejb@linux.ibm.com>,
Min Xu <min.m.xu@intel.com>, Jiewen Yao <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Erdem Aktas <erdemaktas@google.com>,
Michael Roth <Michael.Roth@amd.com>
Subject: Re: [PATCH 0/2] SEV BaseMemEncryptLib cleanup
Date: Fri, 21 Jan 2022 09:04:54 +0100 [thread overview]
Message-ID: <20220121080454.zjzezdtqqgfqmg2c@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220119230332.44888-1-brijesh.singh@amd.com>
On Wed, Jan 19, 2022 at 05:03:30PM -0600, Brijesh Singh wrote:
> This is the first of cleanup for SEV MemEncryptLib. The library uses
> the CPUID followed by the MSR read to determine whether SEV is enabled.
>
> Now that we have a workarea concept, the logic can be simplified to
> store the msr status in workarea and use that to build PCDs and then
> later simply use the PCDs instead of going through the CPUID and RDMSR.
>
> The complete branch is available at
> https://github.com/codomania/edk2/tree/sev-workarea-cleanup
>
> Brijesh Singh (2):
> OvmfPkg/ResetVector: cache the SEV status MSR value in workarea
> OvmfPkg/BaseMemEncryptLib: use the SEV_STATUS MSR value from workarea
Looks good to me.
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
take care,
Gerd
next prev parent reply other threads:[~2022-01-21 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 23:03 [PATCH 0/2] SEV BaseMemEncryptLib cleanup Brijesh Singh
2022-01-19 23:03 ` [PATCH 1/2] OvmfPkg/ResetVector: cache the SEV status MSR value in workarea Brijesh Singh
2022-01-19 23:03 ` [PATCH 2/2] OvmfPkg/BaseMemEncryptLib: use the SEV_STATUS MSR value from workarea Brijesh Singh
2022-01-21 8:04 ` Gerd Hoffmann [this message]
2022-01-25 22:09 ` [edk2-devel] [PATCH 0/2] SEV BaseMemEncryptLib cleanup Brijesh Singh
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=20220121080454.zjzezdtqqgfqmg2c@sirius.home.kraxel.org \
--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