[PATCH 08/10] crypto: ccp - Add support for the RNG in a version 5 CCP

Signed-off-by: Gary R Hook --- drivers/crypto/ccp/ccp-dev-v3.c | 13 - drivers/crypto/ccp/ccp-dev-v5.c |7 +++ drivers/crypto/ccp/ccp-dev.c| 23 +++ drivers/crypto/ccp/ccp-dev.h|2 ++ 4 files changed, 36 insertions(+), 9

[PATCH 04/10] crypto: ccp - Refactor the storage block allocation code

Move the KSB access/management functions to the v3 device file, and add function pointers to the actions structure. At the operations layer all of the references to the storage block will be generic (virtual). This is in preparation for a version 5 device, in which the private storage block is

[PATCH 05/10] crypto: ccp - Refactor code supporting the CCP's RNG

Make the RNG support code common (where possible) in preparation for adding a v5 device. Signed-off-by: Gary R Hook --- drivers/crypto/ccp/ccp-dev-v3.c | 51 --- drivers/crypto/ccp/ccp-dev.c| 28 +

[PATCH 07/10] crypto: ccp - Let a v5 CCP provide the same function as v3

Enable equivalent function on a v5 CCP. Add support for a version 5 CCP which enables AES/XTS/SHA services. Also, more work on the data structures to virtualize functionality. Signed-off-by: Gary R Hook --- drivers/crypto/ccp/Makefile |1

[PATCH 03/10] crypto: ccp - Refactoring: symbol cleanup

Form and use of the local storage block in the CCP is particular to the device version. Much of the code that accesses the storage block can treat it as a virtual resource, and will under go some renaming. Device-specific access to the memory will be moved into device file. Service functions will

[PATCH 01/10] crypto: ccp - Abstract PCI info for the CCP

Device-specific values for the BAR and offset should be found in the version data structure. Signed-off-by: Gary R Hook --- drivers/crypto/ccp/ccp-dev-v3.c |3 +++ drivers/crypto/ccp/ccp-dev.h|3 +++ drivers/crypto/ccp/ccp-pci.c| 15 +++ 3 files

[PATCH 00/10] Enablement of a v5 CCP

The following series updates the CCP driver to support both current and new cryptographic coprocessor models. Refactor code to further separate device-specific code from driver logic, then add equivalent support for the new device version. --- Gary R Hook (10): crypto: ccp - Abstract PCI

[PATCH] crypto: ccp - Fix non-conforming comment style

Adhere to the cryptodev comment convention. Signed-off-by: Gary R Hook --- drivers/crypto/ccp/ccp-dev.h | 24 1 file changed, 8 insertions(+), 16 deletions(-) diff --git a/drivers/crypto/ccp/ccp-dev.h b/drivers/crypto/ccp/ccp-dev.h index

Re: a few questions on AF_ALG specification (AEAD, socket/connection, ...)

Hi, On 07/26/2016 04:54 AM, Stephan Mueller wrote: >> > Is it true that the key (defined via setsockopt) is common to all the >> > connections but the IV (defined through message control header) is >> > specific to each connection ? > Yes. I think that's not correct. Please define a "connection".

Re: a few questions on AF_ALG specification (AEAD, socket/connection, ...)

Am Dienstag, 26. Juli 2016, 13:48:21 CEST schrieb Nicolas Brunie: Hi Nicolas, > Hi All, > I am developping a driver for a crypto offloading solution which > uses the AF_ALG interface. I am trying to stay as close as possible to > the specification but apart from the kernel crypto source code

a few questions on AF_ALG specification (AEAD, socket/connection, ...)

Hi All, I am developping a driver for a crypto offloading solution which uses the AF_ALG interface. I am trying to stay as close as possible to the specification but apart from the kernel crypto source code and a few documents (such as