diff options
| author | Brijesh Singh <brijesh.singh@amd.com> | 2022-04-26 18:01:31 +0000 |
|---|---|---|
| committer | Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> | 2022-07-13 17:27:26 -0500 |
| commit | 0543aac866ffb4e6030031068e93d8031edf7a8e (patch) | |
| tree | 487d16460cf7beaa9e7aea341b2f751b54fdb2bb /scripts/objdiff | |
| parent | 4e17935aa337ca3dae1683c55257e2da267c83ce (diff) | |
| download | cachepc-linux-0543aac866ffb4e6030031068e93d8031edf7a8e.tar.gz cachepc-linux-0543aac866ffb4e6030031068e93d8031edf7a8e.zip | |
crypto: ccp: Handle the legacy TMR allocation when SNP is enabled
The behavior and requirement for the SEV-legacy command is altered when
the SNP firmware is in the INIT state. See SEV-SNP firmware specification
for more details.
Allocate the Trusted Memory Region (TMR) as a 2mb sized/aligned region
when SNP is enabled to satify new requirements for the SNP. Continue
allocating a 1mb region for !SNP configuration.
While at it, provide API that can be used by others to allocate a page
that can be used by the firmware. The immediate user for this API will
be the KVM driver. The KVM driver to need to allocate a firmware context
page during the guest creation. The context page need to be updated
by the firmware. See the SEV-SNP specification for further details.
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions