From: "Gonglei (Arei)" <arei.gonglei@huawei.com>
To: Bibo Mao <maobibo@loongson.cn>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>,
QEMU devel <qemu-devel@nongnu.org>
Subject: RE: virtio-crypto: Inquiry about virtio crypto
Date: Thu, 27 Nov 2025 02:56:51 +0000 [thread overview]
Message-ID: <027ff08db97d414da0ccc24a439e75d0@huawei.com> (raw)
In-Reply-To: <d4258604-e678-f975-0733-71190cf4067d@loongson.cn>
Hi,
> -----Original Message-----
> From: Bibo Mao <maobibo@loongson.cn>
> Sent: Thursday, November 27, 2025 9:43 AM
> To: Gonglei (Arei) <arei.gonglei@huawei.com>
> Cc: linux-crypto@vger.kernel.org; virtualization@lists.linux.dev; linux-kernel
> <linux-kernel@vger.kernel.org>; QEMU devel <qemu-devel@nongnu.org>
> Subject: virtio-crypto: Inquiry about virtio crypto
>
> Hi gonglei,
>
> I am investigating how to use HW crypto accelerator in VM. It seems that
> virtio-crypto is one option, however only aes skcipher algo is supported and
Actually akcipher service had been supported by virtio-crypto in 2022.
> virtio-crypto device is not suggested by RHEL 10.
>
> https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html
> /configuring_and_managing_linux_virtual_machines/feature-support-and-limit
> ations-in-rhel-10-virtualization
>
> I want to know what is the potential issued with virtio-crypto.
>
This question is too big, maybe you'd better ask RHEL guys. :(
Regards,
-Gonglei
> Regards
> Bibo Mao
next prev parent reply other threads:[~2025-11-27 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 1:43 virtio-crypto: Inquiry about virtio crypto Bibo Mao
2025-11-27 2:56 ` Gonglei (Arei) [this message]
2025-11-27 3:09 ` Bibo Mao
2025-11-27 9:38 ` Bibo Mao
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=027ff08db97d414da0ccc24a439e75d0@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux.dev \
/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.