From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqNg6-0008Pa-EF for qemu-devel@nongnu.org; Wed, 13 Apr 2016 12:30:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aqNg3-000201-8v for qemu-devel@nongnu.org; Wed, 13 Apr 2016 12:30:06 -0400 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:50857) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqNg2-0001zS-Vj for qemu-devel@nongnu.org; Wed, 13 Apr 2016 12:30:03 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 13 Apr 2016 17:30:01 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (d06relay09.portsmouth.uk.ibm.com [9.149.109.194]) by d06dlp01.portsmouth.uk.ibm.com (Postfix) with ESMTP id C797917D8063 for ; Wed, 13 Apr 2016 17:30:42 +0100 (BST) Received: from d06av05.portsmouth.uk.ibm.com (d06av05.portsmouth.uk.ibm.com [9.149.37.229]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u3DGTwLu8389108 for ; Wed, 13 Apr 2016 16:29:58 GMT Received: from d06av05.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av05.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u3DGTvod014581 for ; Wed, 13 Apr 2016 10:29:58 -0600 Date: Wed, 13 Apr 2016 18:29:55 +0200 From: Cornelia Huck Message-ID: <20160413182955.74e6c950.cornelia.huck@de.ibm.com> In-Reply-To: <33183CC9F5247A488A2544077AF19020B03132BA@SZXEMA503-MBS.china.huawei.com> References: <33183CC9F5247A488A2544077AF19020B030EDAE@SZXEMA503-MBS.china.huawei.com> <20160412100017.2c522f94.cornelia.huck@de.ibm.com> <33183CC9F5247A488A2544077AF19020B03132BA@SZXEMA503-MBS.china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: "virtio-dev@lists.oasis-open.org" , "qemu-devel@nongnu.org" , "mst@redhat.com" , "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 , =?UTF-8?B?J0ZyYW7Dp29pcy1GcsOp?= =?UTF-8?B?ZMOpcmlj?= Ozog' , "'Venkatesan, Venky'" , Catalin Vasile On Tue, 12 Apr 2016 09:03:33 +0000 "Gonglei (Arei)" wrote: > > From: Cornelia Huck [mailto:cornelia.huck@de.ibm.com] > > Sent: Tuesday, April 12, 2016 4:00 PM > > Subject: Re: [RFC v2] virtio-crypto specification > > > > On Tue, 5 Apr 2016 09:14:09 +0000 > > "Gonglei (Arei)" wrote: > > > > > > > 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.