From: Brijesh Singh <brijesh.singh@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <brijesh.singh@amd.com>, <thomas.lendacky@amd.com>,
<herbert@gondor.apana.org.au>, <arnd@arndb.de>,
<lambert.quentin@gmail.com>, <gary.hook@amd.com>,
<linux-kernel@vger.kernel.org>, <Julia.Lawall@lip6.fr>,
<weiyongjun1@huawei.com>, <linux-crypto@vger.kernel.org>,
<umgwanakikbuti@gmail.com>
Subject: Re: [PATCH 0/2] Introduce AMD Secure Processor device
Date: Thu, 19 Jan 2017 14:03:12 -0600 [thread overview]
Message-ID: <0442f536-221d-fcef-3009-4bc07403ccd8@amd.com> (raw)
In-Reply-To: <20170119182101.GB30851@kroah.com>
Hi Greg,
On 01/19/2017 12:21 PM, Greg KH wrote:
> On Thu, Jan 19, 2017 at 01:07:50PM -0500, Brijesh Singh wrote:
>> The 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 moves the CCP device driver to the misc directory and
>> creates a framework that allows functional component of the AMD Secure
>> Processor to be initialized and handled appropriately.
>
> Why the misc directory? I don't see the justification here...
>
Since this driver is not solely for crypto purposes and do not fit in
any of the standard categories hence I thought of moving it into misc
directory. I am open to other suggestions unless Herbert is ok with
leaving it into crypto and allowing the addition of the Secure Processor
support.
The patch series allows the CCP driver to support other Secure Processor
functions, e.g Secure Encrypted Virtualization (SEV) key management. In
past, I tried to add SEV support into existing CCP driver [1] but we
quickly learned that CCP driver should be moved outside the crypto
directory otherwise will end up adding non crypto code into
drivers/crypto directory. Once this cleanup is accepted then I can work
to add SEV support inside the CCP driver.
[1] http://marc.info/?l=linux-kernel&m=147204118426151&w=2
-Brijesh
next prev parent reply other threads:[~2017-01-19 20:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 18:07 Brijesh Singh
2017-01-19 18:08 ` [PATCH 1/2] crypto: move CCP device driver to misc Brijesh Singh
2017-01-19 18:18 ` Greg KH
2017-01-19 19:10 ` Brijesh Singh
2017-01-20 16:33 ` kbuild test robot
2017-01-19 18:08 ` [PATCH 2/2] misc: amd-sp: introduce the AMD Secure Processor device Brijesh Singh
2017-01-19 18:22 ` Greg KH
2017-01-20 16:20 ` kbuild test robot
2017-01-20 19:51 ` kbuild test robot
2017-01-19 18:21 ` [PATCH 0/2] Introduce " Greg KH
2017-01-19 20:03 ` Brijesh Singh [this message]
2017-01-20 8:45 ` Greg KH
2017-01-20 15:40 ` Brijesh Singh
2017-01-20 17:39 ` Greg KH
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=0442f536-221d-fcef-3009-4bc07403ccd8@amd.com \
--to=brijesh.singh@amd.com \
--cc=Julia.Lawall@lip6.fr \
--cc=arnd@arndb.de \
--cc=gary.hook@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=lambert.quentin@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=umgwanakikbuti@gmail.com \
--cc=weiyongjun1@huawei.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
all inboxes | Powered by JetHome®