From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
peter.huangpeng@huawei.com, luonengjun@huawei.com,
cornelia.huck@de.ibm.com, stefanha@redhat.com,
denglingli@chinamobile.com, Jani.Kokkonen@huawei.com,
Ola.Liljedahl@arm.com, Varun.Sethi@freescale.com,
xin.zeng@intel.com, brian.a.keating@intel.com,
liang.j.ma@intel.com, john.griffin@intel.com,
hanweidong@huawei.com, weidong.huang@huawei.com
Subject: Re: [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification
Date: Wed, 3 Aug 2016 17:30:22 +0300 [thread overview]
Message-ID: <20160803172932-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1470043221-37728-1-git-send-email-arei.gonglei@huawei.com>
On Mon, Aug 01, 2016 at 05:20:19PM +0800, Gonglei wrote:
> This is the specification (version 6) about a new virtio crypto device.
> After a big reconstruction, the spec (symmetric algos) is near to stabilize.
> This version fix some problems of formating and return value, etc.
>
> If you have any comments, please let me know, thanks :)
You might want to open a jira tracker in oasis jira to add this.
> CC: Michael S. Tsirkin <mst@redhat.com>
> CC: Cornelia Huck <cornelia.huck@de.ibm.com>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Lingli Deng <denglingli@chinamobile.com>
> CC: Jani Kokkonen <Jani.Kokkonen@huawei.com>
> CC: Ola Liljedahl <Ola.Liljedahl@arm.com>
> CC: Varun Sethi <Varun.Sethi@freescale.com>
> CC: Zeng Xin <xin.zeng@intel.com>
> CC: Keating Brian <brian.a.keating@intel.com>
> CC: Ma Liang J <liang.j.ma@intel.com>
> CC: Griffin John <john.griffin@intel.com>
> CC: Hanweidong <hanweidong@huawei.com>
>
> Changes from v6:
> - add conformance clauses for virtio crypto device. [Michael]
> - drop VIRTIO_CRYPTO_S_STARTED. [Michael]
> - fix some characters problems. [Stefan]
> - add a MAC algorithm, named VIRTIO_CRYPTO_MAC_ZUC_EIA3. [Zeng Xin]
> - add the fourth return code, named VIRTIO_CRYPTO_OP_INVSESS used
> for invalid session id when executing crypto operations.
> - drop some gpu stuff forgot to delete. [Michael]
> - convert tab to space all over the content.
>
> Changes from v4:
> - introduce crypto services into virtio crypto device. The services
> currently defined are CIPHER, MAC, HASH, AEAD, KDF, ASYM, PRIMITIVE.
> - define a unified crypto request format that is consisted of
> general header + service specific request, Where 'general header' is for all
> crypto request, 'service specific request' is composed of
> operation parameter + input data + output data in generally.
> operation parameter is algorithm-specific parameters,
> input data is the data should be operated ,
> output data is the "operation result + result buffer".
> - redefine the algorithms and structure based on above crypto services.
> - rearrange the title and subtitle
> - Only support CIPHER, MAC, HASH and AEAD crypto services, and Xin will
> focus KDF, ASYM and PRIMITIVE services.
> - Some other corresponding fixes.
> - Make a formal patch using tex type.
>
> This version is a big reconstruction based on Zeng, Xin' comments, thanks a lot.
>
> Changes from v3:
> - Don't use enum is the spec but macros in specific structures. [Michael & Stefan]
> - Add two complete structures for session creation and closing, so that
> the spec is clear on how to lay out the request. [Stefan]
> - Definite the crypto operation request with assigned structure, in this way,
> each data request only occupies *one entry* of the Vring descriptor table,
> which *improves* the *throughput* of data transferring.
>
> Changes from v2:
> - Reserve virtio device ID 20 for crypto device. [Cornelia]
> - Drop all feature bits, those capabilities are offered by the device all the time. [Stefan & Cornelia]
> - Add a new section 1.4.2 for driver requirements. [Stefan]
> - Use definite type definition instead of enum type in some structure. [Stefan]
> - Add virtio_crypto_cipher_alg definition. [Stefan]
> - Add a "Device requirements" section as using MUST. [Stefan]
> - Some grammar nits fixes and typo fixes. [Stefan & Cornelia]
> - Add one VIRTIO_CRYPTO_S_STARTED status for the driver as the flag of virtio-crypto device started and can work now.
>
> Great thanks for Stefan and Cornelia!
>
> Changes from v1:
> - Drop the feature bit definition for each algorithm, and using config space instead [Cornelia]
> - Add multiqueue support and add corresponding feature bit
> - Update Encryption process and header definition
> - Add session operation process and add corresponding header description
> - Other better description in order to fit for virtio spec [Michael]
> - Some other trivial fixes.
>
>
> Gonglei (2):
> virtio-crypto: Add virtio crypto device specification
> virtio-crypto: Add conformance clauses
>
> conformance.tex | 30 +++
> content.tex | 2 +
> virtio-crypto.tex | 793 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 825 insertions(+)
> create mode 100644 virtio-crypto.tex
>
> --
> 1.7.12.4
>
next prev parent reply other threads:[~2016-08-03 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:20 [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification Gonglei
2016-08-01 9:20 ` [Qemu-devel] [PATCH v6 1/2] virtio-crypto: Add " Gonglei
2016-08-04 7:48 ` Zeng, Xin
2016-08-04 11:24 ` Gonglei (Arei)
2016-08-04 19:56 ` Michael S. Tsirkin
2016-08-08 6:27 ` Zeng, Xin
2016-08-09 10:44 ` Cornelia Huck
2016-08-09 13:42 ` Zeng, Xin
2016-08-09 10:58 ` Michael S. Tsirkin
2016-08-09 13:42 ` Zeng, Xin
2016-08-10 1:11 ` Gonglei (Arei)
2016-08-01 9:20 ` [Qemu-devel] [PATCH v6 2/2] virtio-crypto: add conformance clauses Gonglei
2016-08-03 14:30 ` Michael S. Tsirkin [this message]
2016-08-03 14:33 ` [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification Cornelia Huck
2016-08-03 14:40 ` Michael S. Tsirkin
2016-08-03 14:53 ` Cornelia Huck
2016-08-03 17:23 ` Cornelia Huck
2016-08-03 18:40 ` Michael S. Tsirkin
2016-08-04 19:50 ` Michael S. Tsirkin
2016-08-03 15:17 ` Zeng, Xin
2016-08-03 15:46 ` Michael S. Tsirkin
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=20160803172932-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=Ola.Liljedahl@arm.com \
--cc=Varun.Sethi@freescale.com \
--cc=arei.gonglei@huawei.com \
--cc=brian.a.keating@intel.com \
--cc=cornelia.huck@de.ibm.com \
--cc=denglingli@chinamobile.com \
--cc=hanweidong@huawei.com \
--cc=john.griffin@intel.com \
--cc=liang.j.ma@intel.com \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=weidong.huang@huawei.com \
--cc=xin.zeng@intel.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).