From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xuquan8@huawei.com, arei.gonglei@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.10 14/19] crypto: cipher: add af_alg cipher support
Date: Mon, 10 Apr 2017 18:52:29 +0800 [thread overview]
Message-ID: <58EB63ED.4020504@huawei.com> (raw)
In-Reply-To: <20170410101853.GI3655@redhat.com>
On 2017/4/10 18:18, Daniel P. Berrange wrote:
> On Mon, Apr 10, 2017 at 05:00:52PM +0800, Longpeng(Mike) wrote:
>> Adds afalg-backend cipher support: introduces some private APIs
>> firstly, and then intergrates them into qcrypto_cipher_afalg_driver.
>>
>> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
>> ---
>> crypto/Makefile.objs | 1 +
>> crypto/cipher-afalg.c | 229 ++++++++++++++++++++++++++++++++++++++++++++
>> crypto/cipher.c | 30 +++++-
>> include/crypto/afalg-comm.h | 11 +++
>> include/crypto/cipher.h | 7 ++
>> tests/test-crypto-cipher.c | 10 +-
>> 6 files changed, 286 insertions(+), 2 deletions(-)
>> create mode 100644 crypto/cipher-afalg.c
>>
>
...
>
>
> All methods in this file should be named 'qcrypto_afalg_...'
>
Hi Daniel,
Now the libiary-backend methods are named as "nettle(gcrypt,glib,builtin)_...",
so if I rename them with "qcrypto_afalg_" prefix , then the libiary-backend
methods need with "qcrypto_nettle(gcrypt,glib,builtin)_" prefix , right ?
>> +
>> +struct QCryptoCipherDriver qcrypto_cipher_afalg_driver = {
>> + .cipher_encrypt = afalg_cipher_encrypt,
>> + .cipher_decrypt = afalg_cipher_decrypt,
>> + .cipher_setiv = afalg_cipher_setiv,
>> + .cipher_free = afalg_comm_ctx_free,
>> +};
>
>
>
>
> Regards,
> Daniel
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2017-04-10 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:00 [Qemu-devel] [PATCH for-2.10 14/19] crypto: cipher: add af_alg cipher support Longpeng(Mike)
2017-04-10 10:18 ` Daniel P. Berrange
2017-04-10 10:52 ` Longpeng (Mike) [this message]
2017-04-10 10:56 ` Daniel P. Berrange
2017-04-10 10:59 ` Longpeng (Mike)
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=58EB63ED.4020504@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xuquan8@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;
as well as URLs for NNTP newsgroup(s).