lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 8 Nov 2012 07:47:25 -0800 (PST) From: Andy King <acking@...are.com> To: Gerd Hoffmann <kraxel@...hat.com> Cc: David Miller <davem@...emloft.net>, pv-drivers@...are.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, virtualization@...ts.linux-foundation.org, gregkh@...uxfoundation.org, georgezhang@...are.com Subject: Re: [Pv-drivers] [PATCH 0/6] VSOCK for Linux upstreaming Hi Gerd, >> Also, there was some interest from RedHat into using vSockets as >> a unified interface, routed over a hypervisor-specific transport >> (virtio or otherwise, although for now VMCI is the only one >> implemented). > > Can you outline how this can be done? From a quick look over the > code it seems like vsock has a hard dependency on vmci, is that > correct? That's correct, VMCI is wired into vSockets and we don't currently provide any way to insert another transport. > When making vsock a generic, reusable kernel service it should be > the other way around: vsock should provide the core implementation > and an interface where hypervisor-specific transports (vmci, > virtio, xenbus, ...) can register themself. Sorry, that was a bad explanation on my part. You're absolutely correct as to how it _should_ work. But it's up to Red Hat or others to get the ball rolling and motivate the necessary work on vSockets to make this happen. As Greg says, "everyone is lazy and just wants their code accepted" ;) Thanks! - Andy -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists