From: "Gonglei (Arei)" <arei.gonglei@huawei.com>
To: zhenwei pi <pizhenwei@bytedance.com>, "mst@redhat.com" <mst@redhat.com>
Cc: "jasowang@redhat.com" <jasowang@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"helei.sig11@bytedance.com" <helei.sig11@bytedance.com>
Subject: RE: [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC
Date: Thu, 10 Feb 2022 07:22:24 +0000 [thread overview]
Message-ID: <fac2cfd89f3f4fff9e5c5d29c8c4ed8a@huawei.com> (raw)
In-Reply-To: <20220121022438.1042547-2-pizhenwei@bytedance.com>
> -----Original Message-----
> From: zhenwei pi [mailto:pizhenwei@bytedance.com]
> Sent: Friday, January 21, 2022 10:25 AM
> To: mst@redhat.com; Gonglei (Arei) <arei.gonglei@huawei.com>
> Cc: jasowang@redhat.com; virtualization@lists.linux-foundation.org;
> linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org;
> helei.sig11@bytedance.com; zhenwei pi <pizhenwei@bytedance.com>
> Subject: [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC
>
> Base on the lastest virtio crypto spec, define VIRTIO_CRYPTO_NOSPC.
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> include/uapi/linux/virtio_crypto.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/virtio_crypto.h
> b/include/uapi/linux/virtio_crypto.h
> index a03932f10565..1166a49084b0 100644
> --- a/include/uapi/linux/virtio_crypto.h
> +++ b/include/uapi/linux/virtio_crypto.h
> @@ -408,6 +408,7 @@ struct virtio_crypto_op_data_req {
> #define VIRTIO_CRYPTO_BADMSG 2
> #define VIRTIO_CRYPTO_NOTSUPP 3
> #define VIRTIO_CRYPTO_INVSESS 4 /* Invalid session id */
> +#define VIRTIO_CRYPTO_NOSPC 5 /* no free session ID */
>
> /* The accelerator hardware is ready */ #define
> VIRTIO_CRYPTO_S_HW_READY (1 << 0)
> --
> 2.25.1
Reviewed-by: Gonglei <arei.gonglei@huawei.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Gonglei \(Arei\) via Virtualization" <virtualization@lists.linux-foundation.org>
To: zhenwei pi <pizhenwei@bytedance.com>, "mst@redhat.com" <mst@redhat.com>
Cc: "helei.sig11@bytedance.com" <helei.sig11@bytedance.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: RE: [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC
Date: Thu, 10 Feb 2022 07:22:24 +0000 [thread overview]
Message-ID: <fac2cfd89f3f4fff9e5c5d29c8c4ed8a@huawei.com> (raw)
In-Reply-To: <20220121022438.1042547-2-pizhenwei@bytedance.com>
> -----Original Message-----
> From: zhenwei pi [mailto:pizhenwei@bytedance.com]
> Sent: Friday, January 21, 2022 10:25 AM
> To: mst@redhat.com; Gonglei (Arei) <arei.gonglei@huawei.com>
> Cc: jasowang@redhat.com; virtualization@lists.linux-foundation.org;
> linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org;
> helei.sig11@bytedance.com; zhenwei pi <pizhenwei@bytedance.com>
> Subject: [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC
>
> Base on the lastest virtio crypto spec, define VIRTIO_CRYPTO_NOSPC.
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> include/uapi/linux/virtio_crypto.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/virtio_crypto.h
> b/include/uapi/linux/virtio_crypto.h
> index a03932f10565..1166a49084b0 100644
> --- a/include/uapi/linux/virtio_crypto.h
> +++ b/include/uapi/linux/virtio_crypto.h
> @@ -408,6 +408,7 @@ struct virtio_crypto_op_data_req {
> #define VIRTIO_CRYPTO_BADMSG 2
> #define VIRTIO_CRYPTO_NOTSUPP 3
> #define VIRTIO_CRYPTO_INVSESS 4 /* Invalid session id */
> +#define VIRTIO_CRYPTO_NOSPC 5 /* no free session ID */
>
> /* The accelerator hardware is ready */ #define
> VIRTIO_CRYPTO_S_HW_READY (1 << 0)
> --
> 2.25.1
Reviewed-by: Gonglei <arei.gonglei@huawei.com>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-02-10 7:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 2:24 [PATCH 0/3] Introduce akcipher service for virtio-crypto zhenwei pi
2022-01-21 2:24 ` zhenwei pi
2022-01-21 2:24 ` [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC zhenwei pi
2022-01-21 2:24 ` zhenwei pi
2022-02-10 7:22 ` Gonglei (Arei) [this message]
2022-02-10 7:22 ` Gonglei (Arei) via Virtualization
2022-01-21 2:24 ` [PATCH 2/3] virtio-crypto: introduce akcipher service zhenwei pi
2022-01-21 2:24 ` zhenwei pi
2022-02-10 7:51 ` Gonglei (Arei)
2022-02-10 7:51 ` Gonglei (Arei) via Virtualization
2022-02-10 8:18 ` zhenwei pi
2022-02-10 8:18 ` zhenwei pi
2022-02-10 9:21 ` Gonglei (Arei)
2022-02-10 9:21 ` Gonglei (Arei) via Virtualization
2022-01-21 2:24 ` [PATCH 3/3] virtio-crypto: implement RSA algorithm zhenwei pi
2022-01-21 2:24 ` zhenwei pi
2022-01-21 6:36 ` kernel test robot
2022-01-21 6:36 ` kernel test robot
2022-01-21 6:36 ` kernel test robot
2022-01-21 8:29 ` [RFC PATCH] virtio-crypto: virtio_crypto_rsa_do_req() can be static kernel test robot
2022-01-21 8:29 ` kernel test robot
2022-01-21 8:29 ` kernel test robot
2022-01-21 8:39 ` [PATCH 3/3] virtio-crypto: implement RSA algorithm kernel test robot
2022-01-21 8:39 ` kernel test robot
2022-01-21 8:39 ` kernel test robot
2022-01-21 21:43 ` kernel test robot
2022-01-21 21:43 ` kernel test robot
2022-01-21 21:43 ` kernel test robot
2022-01-22 0:19 ` kernel test robot
2022-01-22 0:19 ` kernel test robot
2022-01-22 0:19 ` kernel test robot
2022-02-10 6:55 ` PING: [PATCH 0/3] Introduce akcipher service for virtio-crypto zhenwei pi
2022-02-10 6:55 ` zhenwei pi
2022-02-10 7:17 ` Jason Wang
2022-02-10 7:17 ` Jason Wang
2022-02-10 7:23 ` Michael S. Tsirkin
2022-02-10 7:23 ` Michael S. Tsirkin
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=fac2cfd89f3f4fff9e5c5d29c8c4ed8a@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.com \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=virtualization@lists.linux-foundation.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.