From: Brijesh Singh <brijesh.singh@amd.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: brijesh.singh@amd.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, "Hook, Gary" <Gary.Hook@amd.com>,
thomas.lendacky@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net
Subject: Re: [PATCH 0/3] Introduce AMD Secure Processor device
Date: Fri, 23 Jun 2017 16:23:59 -0500 [thread overview]
Message-ID: <771a32f1-4afb-daf8-2da5-3f9e5c7a4551@amd.com> (raw)
In-Reply-To: <20170622132539.GA14239@localhost>
On 06/22/2017 08:25 AM, Pavel Machek wrote:
> On Thu 2017-06-22 06:42:01, Brijesh Singh wrote:
>> CCP device (drivers/crypto/ccp/ccp.ko) is part of AMD Secure Processor,
>> which is not dedicated solely to crypto. The AMD Secure Processor includes
>> CCP and PSP (Platform Secure Processor) devices.
>>
>> This patch series adds a framework that allows functional component of the
>> AMD Secure Processor to be initialized and handled appropriately. The series
>> does not makes any logic modification into CCP - it refactors the code to
>> integerate CCP into AMD secure processor framework.
>
> Ok, so this is just preparation. When finished, what services will it provide
> to Linux userland?
Yes, this is in preparation to add PSP [1] and SEV (Secure Encrypted Virtualization)
[2] support. When finished, the SEV will provide:
a) in-kernel API to communicate with SEV FW inside the AMD Secure Processor
b) userspace ioctl to manage the platform keys/certificates
I have posted PSP and SEV patches as part of SEV RFC, see below
[1] http://marc.info/?l=linux-mm&m=148846780431232&w=2
[2] http://marc.info/?l=linux-mm&m=148847075032602&w=2
-Brijesh
prev parent reply other threads:[~2017-06-23 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 11:42 [PATCH 0/3] Introduce AMD Secure Processor device Brijesh Singh
2017-06-22 11:42 ` [PATCH 1/3] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup Brijesh Singh
2017-06-22 11:42 ` [PATCH 2/3] crypto: ccp - Introduce the AMD Secure Processor device Brijesh Singh
2017-06-22 11:42 ` [PATCH 3/3] crypto: cpp - Abstract interrupt registeration Brijesh Singh
2017-06-22 13:25 ` [PATCH 0/3] Introduce AMD Secure Processor device Pavel Machek
2017-06-23 21:23 ` Brijesh Singh [this message]
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=771a32f1-4afb-daf8-2da5-3f9e5c7a4551@amd.com \
--to=brijesh.singh@amd.com \
--cc=Gary.Hook@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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