From: Viktor VM Mihajlovski <mihajlov@linux.vnet.ibm.com>
To: "Farhan Ali" <alifm@linux.ibm.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
qemu-devel@nongnu.org, frankja@linux.ibm.com, mst@redhat.com,
borntraeger@de.ibm.com, arei.gonglei@huawei.com,
longpeng2@huawei.com, mjrosato@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC v1 1/1] virtio-crypto: Allow disabling of cipher algorithms for virtio-crypto device
Date: Mon, 18 Jun 2018 12:27:59 +0200 [thread overview]
Message-ID: <f8b2d1d2-2747-dbe5-3b02-f84e2f401972@linux.vnet.ibm.com> (raw)
In-Reply-To: <ca88315c-75a0-ddc2-ba81-e1dfdb2d6d25@linux.ibm.com>
On 15.06.2018 17:10, Farhan Ali wrote:
>
>
> On 06/15/2018 09:17 AM, Viktor VM Mihajlovski wrote:
[...]
>>
>> With the current virtio-crypto backend functionality offered (CBC AES
>> only) it may seem a bit over-engineered to offer a configuration option
>> to remove the only supported algorithm...
>>
>> What I could imagine to be useful though, would be to allow the backend
>> to advertise its capabilities to the guest virtio-crypto device, so that
>> the guest driver can register the algorithms supported dynamically.
>> Currently, the algorithms are hard-coded on both sides which makes it a
>> bit hard to extend the backends to support new algorithms (or write new
>> backends if so desired).
>
> I posted some kernel patches
> (https://www.spinics.net/lists/kvm/msg170332.html), that takes care of
> registering algorithms based on what the backend advertises.
>
Sorry, I missed that. Sounds as if the principal mechanism to configure
guest virtio-crypto based on the host capabilities would be established
with the patches.
>
>>
>> Whether the backend itself was configurable would be of less importance
>> then (but still could make sense).
>>
>
>
--
Regards,
Viktor Mihajlovski
next prev parent reply other threads:[~2018-06-18 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1528832686.git.alifm@linux.ibm.com>
2018-06-12 19:48 ` [Qemu-devel] [RFC v1 1/1] virtio-crypto: Allow disabling of cipher algorithms for virtio-crypto device Farhan Ali
2018-06-13 0:57 ` Gonglei (Arei)
2018-06-13 20:14 ` Farhan Ali
2018-06-13 9:37 ` Daniel P. Berrangé
2018-06-13 15:01 ` Farhan Ali
2018-06-13 15:05 ` Daniel P. Berrangé
2018-06-13 17:28 ` Halil Pasic
2018-06-14 8:21 ` Daniel P. Berrangé
2018-06-14 14:50 ` Farhan Ali
2018-06-14 15:10 ` Daniel P. Berrangé
2018-06-14 16:12 ` Farhan Ali
2018-06-14 16:15 ` Daniel P. Berrangé
2018-06-15 13:17 ` Viktor VM Mihajlovski
2018-06-15 15:10 ` Farhan Ali
2018-06-18 10:27 ` Viktor VM Mihajlovski [this message]
2018-06-15 0:52 ` Gonglei (Arei)
2018-06-15 9:26 ` Daniel P. Berrangé
2018-06-15 13:07 ` Christian Borntraeger
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=f8b2d1d2-2747-dbe5-3b02-f84e2f401972@linux.vnet.ibm.com \
--to=mihajlov@linux.vnet.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=longpeng2@huawei.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.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.