From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: longpeng <longpeng2@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
"Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>,
"brian.a.keating@intel.com" <brian.a.keating@intel.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>,
"mst@redhat.com" <mst@redhat.com>,
"xin.zeng@intel.com" <xin.zeng@intel.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Luonengjun <luonengjun@huawei.com>,
"agraf@suse.de" <agraf@suse.de>,
"john.griffin@intel.com" <john.griffin@intel.com>,
"liang.j.ma@intel.com" <liang.j.ma@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"Zhoujian (jay)" <jianjay.zhou@huawei.com>,
"cornelia.huck@de.ibm.com" <cornelia.huck@de.ibm.com>,
"Varun.Sethi@freescale.com" <Varun.Sethi@freescale.com>,
Jani Kokkonen <Jani.Kokkonen@huawei.com>,
"vincent.jardin@6wind.com" <vincent.jardin@6wind.com>,
"denglingli@chinamobile.com" <denglingli@chinamobile.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>
Subject: Re: [Qemu-devel] [v21 RESEND 0/2] virtio-crypto: virtio crypto device specification
Date: Fri, 10 Nov 2017 15:50:52 +0000 [thread overview]
Message-ID: <20171110155052.GD17290@stefanha-x1.localdomain> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA461542@DGGEMA505-MBS.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 4905 bytes --]
On Mon, Nov 06, 2017 at 10:39:24AM +0000, Gonglei (Arei) wrote:
> Hi guys,
>
> What a long time iteration it is.
>
> Hoping this is the final version if no big arguments exist as
> discussed with Stefan at KVM Forum 2017 this October. People
> can submit patches to fix some grammar issues or little problems,
> and then Xin' can submit the asymmetric crypto services spec
> based on this version.
Yes, I support merging the virtio-crypto spec as soon as technical
concerns are addressed.
English language fixes are more efficiently done as follow-up patches
from native speakers. This way we avoid extra iterations that might
themselves add new English language issues.
I hope others see it the same way. If not, speak up now.
BTW, I am committing myself to proofread the document that goes up for
vote and will send follow-up patches.
> I'll start a vote for virtio crypto device after one week. :)
>
> Please reviewing in time, thanks a lot!
>
>
> Regards,
> -Gonglei
>
>
> > -----Original Message-----
> > From: longpeng
> > Sent: Monday, November 06, 2017 2:59 PM
> > To: qemu-devel@nongnu.org; virtio-dev@lists.oasis-open.org
> > Cc: Luonengjun; mst@redhat.com; cornelia.huck@de.ibm.com;
> > stefanha@redhat.com; denglingli@chinamobile.com; Jani Kokkonen;
> > 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;
> > Huangweidong (C); agraf@suse.de; jasowang@redhat.com;
> > vincent.jardin@6wind.com; Gonglei (Arei); pasic@linux.vnet.ibm.com; wangxin
> > (U); Zhoujian (jay); longpeng
> > Subject: [v21 RESEND 0/2] virtio-crypto: virtio crypto device specification
> >
> > This is the specification about the new virtio crypto device.
> >
> > ---
> > v21 -> v20
> > - rename 'queue_id' to 'reserved' [Halil]
> > - redescribe the format of the structures which using 'union'
> > in the previous version [Halil]
> >
> > v20 -> v19
> > - fix some typos and grammar fixes [Halil]
> > - make queue_id reserved [Halil]
> > - remove 'Steps of Operation'
> >
> > v19 -> v18:
> > - fix some typos and grammar fixes [Stefan, Halil]
> > - rename VIRTIO_CRYPTO_F_STATELESS_MODE to
> > VIRTIO_CRYPTO_F_MUX_MODE
> > - describe the VIRTIO_CRYPTO_STATUS in detial. [Halil]
> > - refactor and redescribe the controlq/dataq request's format
> > of mux mode. [Halil]
> > - other small fixes. [Halil]
> >
> > v18 -> v17:
> > - fix many English grammar problems suggested by Stefan, Thanks a lot!
> >
> > v17 -> v16:
> > - Some grammar fixes [Stefan, Halil, Michael]
> > - add a section named "Supported crypto services" in order to explain bit
> > numbers and valuse clearly. [Halil, Cornelia]
> > - avoid word reptition [Halil]
> > - rename non-session mode to stateless mode [Halil]
> > - change descriptions for all elements in struct virtio_crypto_config [Halil]
> > - add Halil as a reviewer in the ackonwledgement part, thanks for his work.
> > - other fixes here and there.
> >
> > Changes since v15:
> > - use feature bits for non-session mode in order to keep compatibility with
> > pre-existing code. [Halil & Michael]
> > - introduce VIRTIO_CRYPTO_F_ NON_SESSION_MODE feature bit to control all
> > other
> > non-session mode feature bits.
> > - fix some typos. [Stefan]
> > - introduce struct virtio_crypto_op_data_req_mux to support both session
> > and non-session based crypto operations and keep compatibility with
> > pre-existing code.
> >
> > Changes since v14:
> > - drop VIRTIO_CRYPTO_S_STARTED status [Halil & Cornelia]
> > - correct a sentence about dataqueue and controlq in the first paragraph.
> > [Halil]
> > - change a MAY to MUST about max_dataqueues. [Halil]
> > - add non-session mode support
> > a) add four features for different crypto services to identify wheather
> > support session mode.
> > b) rewrite some
> >
> > For pervious versions of virtio crypto spec, Pls see:
> >
> > [v18]:
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg444897.html
> >
> > [v14]:
> > https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg02212.html
> >
> > [v13]:
> > https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07348.html
> >
> > For more information, please see:
> > http://qemu-project.org/Features/VirtioCrypto
> >
> > ---
> > Gonglei (2):
> > virtio-crypto: Add virtio crypto device specification
> > virtio-crypto: Add conformance clauses
> >
> > acknowledgements.tex | 3 +
> > conformance.tex | 29 +
> > content.tex | 2 +
> > virtio-crypto.tex | 1426
> > ++++++++++++++++++++++++++++++++++++++++++++++++++
> > 4 files changed, 1460 insertions(+)
> > create mode 100644 virtio-crypto.tex
> >
> > --
> > 1.8.3.1
> >
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-11-10 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 6:58 [Qemu-devel] [v21 RESEND 0/2] virtio-crypto: virtio crypto device specification Longpeng(Mike)
2017-11-06 6:58 ` [Qemu-devel] [v21 RESEND 1/2] virtio-crypto: Add " Longpeng(Mike)
2017-11-10 17:02 ` Stefan Hajnoczi
2017-11-13 7:33 ` Longpeng (Mike)
2017-11-06 6:58 ` [Qemu-devel] [v21 RESEND 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
2017-11-06 10:39 ` [Qemu-devel] [v21 RESEND 0/2] virtio-crypto: virtio crypto device specification Gonglei (Arei)
2017-11-10 15:50 ` Stefan Hajnoczi [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=20171110155052.GD17290@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=Ola.Liljedahl@arm.com \
--cc=Varun.Sethi@freescale.com \
--cc=agraf@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=brian.a.keating@intel.com \
--cc=cornelia.huck@de.ibm.com \
--cc=denglingli@chinamobile.com \
--cc=jasowang@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=john.griffin@intel.com \
--cc=liang.j.ma@intel.com \
--cc=longpeng2@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=roy.fan.zhang@intel.com \
--cc=stefanha@redhat.com \
--cc=vincent.jardin@6wind.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wangxinxin.wang@huawei.com \
--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).