All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "Cornelia Huck" <cornelia.huck@de.ibm.com>,
	"Crasta Denis-B22176" <denis.crasta@freescale.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"'Ola Liljedahl@arm.com'" <Ola.Liljedahl@arm.com>,
	"'Venkatesan, Venky'" <venky.venkatesan@intel.com>,
	"Hanweidong (Randy)" <hanweidong@huawei.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Mihai Claudiu Caraman" <mike.caraman@nxp.com>,
	"'François-Frédéric Ozog'" <ff.ozog@6wind.com>,
	"Catalin Vasile" <cata.vasile@nxp.com>,
	"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
	"Varun Sethi" <Varun.Sethi@freescale.com>,
	"Jani Kokkonen" <Jani.Kokkonen@huawei.com>,
	"Lingli Deng" <denglingli@chinamobile.com>,
	"'Karlsson, Magnus'" <magnus.karlsson@intel.com>
Subject: Re: [Qemu-devel] [RFC v2] virtio-crypto specification
Date: Thu, 14 Apr 2016 11:26:36 +0100	[thread overview]
Message-ID: <20160414102636.GA7828@stefanha-x1.localdomain> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B031556F@SZXEMA503-MBS.china.huawei.com>

[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]

On Thu, Apr 14, 2016 at 09:26:36AM +0000, Gonglei (Arei) wrote:
> Hi,
> 
> > > > > >
> > > > > > >                  Virtio-crypto device Spec
> > > > > > >
> > > > > > > 1	Crypto Device
> > > > > > > The virtio crypto device is a virtual crypto device (ie. hardware crypto
> > > > > > accelerator card). The encryption and decryption requests of are placed
> > in
> > > > the
> > > > > > data queue, and handled by the real hardware crypto accelerators finally.
> > A
> > > > > > second queue is the control queue, which is used to create or destroy
> > > > session
> > > > > > for symmetric algorithms, and to control some advanced features.
> > > > > > > 1.1	Device ID
> > > > > > > 65535 (experimental)
> > > > > >
> > > > > > I think you should just go ahead and reserve a device ID for this.
> > > > > >
> > > > > OK, I want to reserve 20 as Crypto device's ID as 19 is reserved for Socket
> > > > device.
> > > >
> > > > Just go ahead and send a patch against the virtio spec that reserves it.
> > >
> > > Sorry, I don't find the git repository of virtio spec, except a svn repository
> > which
> > > seems that it's not the latest version. :(
> > >
> > > https://tools.oasis-open.org/version-control/browse/wsvn/virtio/
> > >
> > > Where can I get the git repo address? Thanks.
> > 
> > No git tree, sadly; only the svn repository. The current spec is on the
> > v1.0 branch.
> 
> OK, thanks. Maybe I can use git-svn tool to make patch?

Yes, git-svn works.

The main spec text is in trunk/content.tex.  You also need to modify
trunk/conformance.tex to include all the "Driver Requirements" and
"Device Requirements" sections for your device.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-04-14 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  9:14 [Qemu-devel] [RFC v2] virtio-crypto specification Gonglei (Arei)
2016-04-11  9:43 ` [Qemu-devel] [virtio-dev] " Stefan Hajnoczi
2016-04-11 11:17   ` Gonglei (Arei)
2016-04-12  8:00 ` [Qemu-devel] " Cornelia Huck
2016-04-12  9:03   ` Gonglei (Arei)
2016-04-13 16:29     ` Cornelia Huck
2016-04-14  3:33       ` Gonglei (Arei)
2016-04-14  7:58         ` Cornelia Huck
2016-04-14  9:26           ` Gonglei (Arei)
2016-04-14 10:14             ` Cornelia Huck
2016-04-14 10:22             ` Michael S. Tsirkin
2016-04-14 10:31               ` Gonglei (Arei)
2016-04-14 10:26             ` Stefan Hajnoczi [this message]
2016-04-14 10:36               ` Gonglei (Arei)
2016-04-14 10:45                 ` Cornelia Huck

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=20160414102636.GA7828@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=arei.gonglei@huawei.com \
    --cc=cata.vasile@nxp.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=denis.crasta@freescale.com \
    --cc=ff.ozog@6wind.com \
    --cc=hanweidong@huawei.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=magnus.karlsson@intel.com \
    --cc=mike.caraman@nxp.com \
    --cc=mst@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=venky.venkatesan@intel.com \
    --cc=virtio-dev@lists.oasis-open.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.