I don't get the part with getting cryptodev upstream. I don't know what getting cryptodev upstream actually implies. >From what I know cryptodev is done (is a functional project) that was rejected in the Linux Kernel and there isn't actually way to get it upstream. On Tue, Mar 31, 2015 at 8:14 PM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote: > On Wed, Mar 18, 2015 at 8:59 PM, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: >> On 18/03/2015 18:05, Catalin Vasile wrote: >>> cryptodev is not merged into upstream from what I know. >> >> Yes, but QEMU runs on non-Linux platforms too. Of course doing >> vhost+driver or gnutls+driver would be already more than enough for the >> summer. > > My suggestion is to work on the gnutls driver. Then, if you have time > left, get cryptodev upstream (it can be part of your GSoC project > plan). > > That approach is more beneficial in the long run. It will allow other > applications to use the Crypto API too. > > vhost is good for exploiting kernel-only functionality (usually due to > security/reliability boundaries). In this case the only reason for > vhost is that the userspace API isn't ready yet. Use the opportunity > to contribute to that effort instead of working around it. > > Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
