summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorBrijesh Singh <brijesh.singh@amd.com>2022-04-26 18:06:20 +0000
committerSuravee Suthikulpanit <suravee.suthikulpanit@amd.com>2022-07-13 17:27:27 -0500
commit30443c787ff81af54b328dd70f804862b89f31dc (patch)
treecb53f8731a2b4b5abccceb5233e2c1691e638285 /tools/perf/scripts/python/bin
parent414fdbedf80352fa5a026a8c1676e3fd714c715e (diff)
downloadcachepc-linux-30443c787ff81af54b328dd70f804862b89f31dc.tar.gz
cachepc-linux-30443c787ff81af54b328dd70f804862b89f31dc.zip
crypto: ccp: Add the SNP_{SET,GET}_EXT_CONFIG command
The SEV-SNP firmware provides the SNP_CONFIG command used to set the system-wide configuration value for SNP guests. The information includes the TCB version string to be reported in guest attestation reports. Version 2 of the GHCB specification adds an NAE (SNP extended guest request) that a guest can use to query the reports that include additional certificates. In both cases, userspace provided additional data is included in the attestation reports. The userspace will use the SNP_SET_EXT_CONFIG command to give the certificate blob and the reported TCB version string at once. Note that the specification defines certificate blob with a specific GUID format; the userspace is responsible for building the proper certificate blob. The ioctl treats it an opaque blob. While it is not defined in the spec, but let's add SNP_GET_EXT_CONFIG command that can be used to obtain the data programmed through the SNP_SET_EXT_CONFIG. Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions