From: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
To: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Gary Hook <gary.hook@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Brijesh Singh <brijesh.singh@amd.com>,
Borislav Petkov <bp@suse.de>, Paolo Bonzini <pbonzini@redhat.com>,
Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
Subject: [PATCHv2 0/2] Add new SEV commands
Date: Fri, 25 May 2018 15:23:28 -0500 [thread overview]
Message-ID: <cover.1527274269.git.Janakarajan.Natarajan@amd.com> (raw)
This patchset adds two new SEV commands, introduced in SEV API v0.15
and v0.16 respectively.
* DOWNLOAD_FIRMWARE allows the SEV firmware to be updated if a blob newer
than or similar to the exisiting build is available.
* GET_ID allows to query for a unique ID that can be used to retrieve the
Chip Endorsment Key (CEK) public key signed by the AMD SEV Signing Key
(ASK).
v1->v2:
* Added cover letter.
* Misc changes based on Boris' feedback.
Janakarajan Natarajan (2):
crypto: ccp: Add DOWNLOAD_FIRMWARE SEV command
crypto: ccp: Add GET_ID SEV command
drivers/crypto/ccp/psp-dev.c | 143 ++++++++++++++++++++++++++++++++++++++++---
drivers/crypto/ccp/psp-dev.h | 4 ++
include/linux/psp-sev.h | 23 +++++++
include/uapi/linux/psp-sev.h | 12 ++++
4 files changed, 172 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-25 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 20:23 Janakarajan Natarajan [this message]
2018-05-25 20:23 ` [PATCHv2 1/2] crypto: ccp: Add DOWNLOAD_FIRMWARE SEV command Janakarajan Natarajan
2018-05-25 20:23 ` [PATCHv2 2/2] crypto: ccp: Add GET_ID " Janakarajan Natarajan
2018-05-29 18:46 ` [PATCHv2 0/2] Add new SEV commands Paolo Bonzini
2018-05-29 18:47 ` Gary R Hook
2018-05-30 13:43 ` Brijesh Singh
2018-05-30 16:28 ` Herbert Xu
2018-05-30 18:44 ` Gary R Hook
2018-05-31 6:45 ` Herbert Xu
2018-05-31 12:43 ` Gary R Hook
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-all 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=cover.1527274269.git.Janakarajan.Natarajan@amd.com \
--to=janakarajan.natarajan@amd.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.com \
/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