From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40927) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqeQI-0002Fq-O4 for qemu-devel@nongnu.org; Thu, 14 Apr 2016 06:22:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aqeQE-0007qF-GY for qemu-devel@nongnu.org; Thu, 14 Apr 2016 06:22:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42749) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqeQE-0007qB-91 for qemu-devel@nongnu.org; Thu, 14 Apr 2016 06:22:50 -0400 Date: Thu, 14 Apr 2016 13:22:43 +0300 From: "Michael S. Tsirkin" Message-ID: <20160414130311-mutt-send-email-mst@redhat.com> References: <33183CC9F5247A488A2544077AF19020B030EDAE@SZXEMA503-MBS.china.huawei.com> <20160412100017.2c522f94.cornelia.huck@de.ibm.com> <33183CC9F5247A488A2544077AF19020B03132BA@SZXEMA503-MBS.china.huawei.com> <20160413182955.74e6c950.cornelia.huck@de.ibm.com> <33183CC9F5247A488A2544077AF19020B0313A08@SZXEMA503-MBS.china.huawei.com> <20160414095832.469fce0e.cornelia.huck@de.ibm.com> <33183CC9F5247A488A2544077AF19020B031556F@SZXEMA503-MBS.china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33183CC9F5247A488A2544077AF19020B031556F@SZXEMA503-MBS.china.huawei.com> Subject: Re: [Qemu-devel] [RFC v2] virtio-crypto specification List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Gonglei (Arei)" Cc: Cornelia Huck , "virtio-dev@lists.oasis-open.org" , "qemu-devel@nongnu.org" , "Huangpeng (Peter)" , "Hanweidong (Randy)" , "Zhoujian (jay, Euler)" , Jani Kokkonen , Mihai Claudiu Caraman , Lingli Deng , "'Karlsson, Magnus'" , "'Ola Liljedahl@arm.com'" , Crasta Denis-B22176 , Varun Sethi , =?iso-8859-1?Q?'Fran=E7ois-Fr=E9d=E9ric?= Ozog' , "'Venkatesan, Venky'" , Catalin Vasile 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? > > Regards, > -Gonglei Yes - that's how everyone works. initial clone (takes a very long time): git svn clone -s https://tools.oasis-open.org/version-control/svn/virtio pull git svn rebase push git svn dcommit -- MST