From patchwork Sat Apr 22 06:23:51 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Gonglei (Arei)" X-Patchwork-Id: 9694187 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id BD15F601E9 for ; Sat, 22 Apr 2017 06:29:02 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id AB8E72862D for ; Sat, 22 Apr 2017 06:29:02 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id A024228627; Sat, 22 Apr 2017 06:29:02 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=2.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 1DC9628627 for ; Sat, 22 Apr 2017 06:29:02 +0000 (UTC) Received: from localhost ([::1]:34379 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1oXV-0003ta-DR for patchwork-qemu-devel@patchwork.kernel.org; Sat, 22 Apr 2017 02:29:01 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41131) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1oWa-0003ng-TI for qemu-devel@nongnu.org; Sat, 22 Apr 2017 02:28:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1oWZ-0004ln-3n for qemu-devel@nongnu.org; Sat, 22 Apr 2017 02:28:04 -0400 Received: from szxga03-in.huawei.com ([45.249.212.189]:3393 helo=dggrg03-dlp.huawei.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1d1oWY-0004jP-Fp for qemu-devel@nongnu.org; Sat, 22 Apr 2017 02:28:03 -0400 Received: from 172.30.72.56 (EHLO DGGEML404-HUB.china.huawei.com) ([172.30.72.56]) by dggrg03-dlp.huawei.com (MOS 4.4.6-GA FastPath queued) with ESMTP id AMH58766; Sat, 22 Apr 2017 14:24:09 +0800 (CST) Received: from localhost (10.177.18.62) by DGGEML404-HUB.china.huawei.com (10.3.17.39) with Microsoft SMTP Server id 14.3.301.0; Sat, 22 Apr 2017 14:23:57 +0800 From: Gonglei To: , Date: Sat, 22 Apr 2017 14:23:51 +0800 Message-ID: <1492842231-223720-3-git-send-email-arei.gonglei@huawei.com> X-Mailer: git-send-email 2.8.2.windows.1 In-Reply-To: <1492842231-223720-1-git-send-email-arei.gonglei@huawei.com> References: <1492842231-223720-1-git-send-email-arei.gonglei@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.177.18.62] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58FAF70C.004F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 9884f4b5662e69382300f7a8a20b1c7a X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 45.249.212.189 Subject: [Qemu-devel] [PATCH v18 2/2] virtio-crypto: Add conformance clauses X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: weidong.huang@huawei.com, mst@redhat.com, jasowang@redhat.com, john.griffin@intel.com, amy.zhanghuimin@huawei.com, Varun.Sethi@freescale.com, denglingli@chinamobile.com, arei.gonglei@hotmail.com, agraf@suse.de, Gonglei , nmorey@kalray.eu, lixiao91@huawei.com, vincent.jardin@6wind.com, Ola.Liljedahl@arm.com, zhbzg@huawei.com, luonengjun@huawei.com, xin.zeng@intel.com, linqiangmin@huawei.com, liang.j.ma@intel.com, stefanha@redhat.com, cornelia.huck@de.ibm.com, Jani.Kokkonen@huawei.com, eety.chen@huawei.com, pasic@linux.vnet.ibm.com, brian.a.keating@intel.com, mike.caraman@nxp.com, wu.wubin@huawei.com Errors-To: qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org Sender: "Qemu-devel" X-Virus-Scanned: ClamAV using ClamSMTP Add the conformance targets and clauses for virtio-crypto device. Signed-off-by: Gonglei --- conformance.tex | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/conformance.tex b/conformance.tex index f59e360..7c7a55c 100644 --- a/conformance.tex +++ b/conformance.tex @@ -146,6 +146,21 @@ An SCSI host driver MUST conform to the following normative statements: \item \ref{drivernormative:Device Types / SCSI Host Device / Device Operation / Device Operation: eventq} \end{itemize} +\subsection{Crypto Driver Conformance}\label{sec:Conformance / Driver Conformance / Crypto Driver Conformance} + +An Crypto driver MUST conform to the following normative statements: + +\begin{itemize} +\item \ref{drivernormative:Device Types / Crypto Device / Device configuration layout} +\item \ref{drivernormative:Device Types / Crypto Device / Device Initialization} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / Control Virtqueue / Session operation / Session operation: create session} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / Control Virtqueue / Session operation / Session operation: destroy session} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / HASH Service operation} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / MAC Service operation} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / Symmetric algorithms Operation} +\item \ref{drivernormative:Device Types / Crypto Device / Device Operation / AEAD Service operation} +\end{itemize} + \section{Device Conformance}\label{sec:Conformance / Device Conformance} A device MUST conform to the following normative statements: @@ -267,6 +282,20 @@ An SCSI host device MUST conform to the following normative statements: \item \ref{devicenormative:Device Types / SCSI Host Device / Device Operation / Device Operation: eventq} \end{itemize} +\subsection{Crypto Device Conformance}\label{sec:Conformance / Device Conformance / Crypto Device Conformance} + +An Crypto device MUST conform to the following normative statements: + +\begin{itemize} +\item \ref{devicenormative:Device Types / Crypto Device / Device configuration layout} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / Control Virtqueue / Session operation / Session operation: create session} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / Control Virtqueue / Session operation / Session operation: destroy session} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / HASH Service operation} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / MAC Service operation} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / Symmetric algorithms Operation} +\item \ref{devicenormative:Device Types / Crypto Device / Device Operation / AEAD Service operation} +\end{itemize} + \section{Legacy Interface: Transitional Device and Transitional Driver Conformance}\label{sec:Conformance / Legacy Interface: Transitional Device and