search for: vsock_transport_f_dgram

On Wed, Oct 23, 2019 at 11:55:52AM +0200, Stefano Garzarella wrote: > +static int __init vmci_transport_init(void) > +{ > + int features = VSOCK_TRANSPORT_F_DGRAM; Where is this variable used? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20191027/d6d4f1ef/attac...

...> > This includes: >> > > > > - Per-packet lookup of transports when using sendto(sockaddr_vm) >> > > > > - Selecting H2G or G2H transport using VMADDR_FLAG_TO_HOST and CID in >> > > > > sockaddr_vm >> > > > > - rename VSOCK_TRANSPORT_F_DGRAM to VSOCK_TRANSPORT_F_DGRAM_FALLBACK >> > > > > - connect() now assigns the transport for (similar to connectible >> > > > > sockets) >> > > > > >> > > > > To preserve backwards compatibility with VMCI, some important changes...

..._vsock.h > index 4206dc6d813f..b1c717286993 100644 > --- a/include/net/af_vsock.h > +++ b/include/net/af_vsock.h > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > /* Transport provides DGRAM communication */ > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > +/* Transport provides local (loopback) communication */ > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > struct vsock_transport { > struct module *module; > diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c > index cc8659838bf2..c9e5bad59dc1...

..._vsock.h > index 4206dc6d813f..b1c717286993 100644 > --- a/include/net/af_vsock.h > +++ b/include/net/af_vsock.h > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > /* Transport provides DGRAM communication */ > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > +/* Transport provides local (loopback) communication */ > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > struct vsock_transport { > struct module *module; > diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c > index cc8659838bf2..c9e5bad59dc1...

...gt; > --- a/include/net/af_vsock.h > > > +++ b/include/net/af_vsock.h > > > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > > > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > > > /* Transport provides DGRAM communication */ > > > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > > > +/* Transport provides local (loopback) communication */ > > > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > > > > > struct vsock_transport { > > > struct module *module; > > > diff --git a/net/vmw_vsock/af_vsock.c b/net/...

...gt; > --- a/include/net/af_vsock.h > > > +++ b/include/net/af_vsock.h > > > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > > > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > > > /* Transport provides DGRAM communication */ > > > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > > > +/* Transport provides local (loopback) communication */ > > > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > > > > > struct vsock_transport { > > > struct module *module; > > > diff --git a/net/vmw_vsock/af_vsock.c b/net/...

...; --- a/include/net/af_vsock.h > +++ b/include/net/af_vsock.h > @@ -94,7 +94,13 @@ struct vsock_transport_send_notify_data { > u64 data2; /* Transport-defined. */ > }; > > +#define VSOCK_TRANSPORT_F_H2G 0x00000001 > +#define VSOCK_TRANSPORT_F_G2H 0x00000002 > +#define VSOCK_TRANSPORT_F_DGRAM 0x00000004 Documentation comments, please. > +void vsock_core_unregister(const struct vsock_transport *t) > +{ > + mutex_lock(&vsock_register_mutex); > + > + /* RFC-TODO: maybe we should check if there are open sockets > + * assigned to that transport and avoid the unregis...

...vmci_transport.c +++ b/net/vmw_vsock/vmci_transport.c @@ -2053,19 +2053,22 @@ static bool vmci_check_transport(struct vsock_sock *vsk) return vsk->transport == &vmci_transport; } -static int __init vmci_transport_init(void) +void vmci_vsock_transport_cb(bool is_host) { - int features = VSOCK_TRANSPORT_F_DGRAM | VSOCK_TRANSPORT_F_H2G; - int cid; - int err; + int features; - cid = vmci_get_context_id(); + if (is_host) + features = VSOCK_TRANSPORT_F_H2G; + else + features = VSOCK_TRANSPORT_F_G2H; - if (cid == VMCI_INVALID_ID) - return -EINVAL; + vsock_core_register(&vmci_transport, features); +}...

...efined. */ }; +/* Transport features flags */ +/* Transport provides host->guest communication */ +#define VSOCK_TRANSPORT_F_H2G 0x00000001 +/* Transport provides guest->host communication */ +#define VSOCK_TRANSPORT_F_G2H 0x00000002 +/* Transport provides DGRAM communication */ +#define VSOCK_TRANSPORT_F_DGRAM 0x00000004 + struct vsock_transport { /* Initialize/tear-down socket. */ int (*init)(struct vsock_sock *, struct vsock_sock *); @@ -154,12 +162,8 @@ struct vsock_transport { /**** CORE ****/ -int __vsock_core_init(const struct vsock_transport *t, struct module *owner); -static inline int...

...h index 86f8f463e01a..2a081d19e20d 100644 --- a/include/net/af_vsock.h +++ b/include/net/af_vsock.h @@ -94,7 +94,13 @@ struct vsock_transport_send_notify_data { u64 data2; /* Transport-defined. */ }; +#define VSOCK_TRANSPORT_F_H2G 0x00000001 +#define VSOCK_TRANSPORT_F_G2H 0x00000002 +#define VSOCK_TRANSPORT_F_DGRAM 0x00000004 + struct vsock_transport { + uint64_t features; + /* Initialize/tear-down socket. */ int (*init)(struct vsock_sock *, struct vsock_sock *); void (*destruct)(struct vsock_sock *); @@ -156,12 +162,8 @@ struct vsock_transport { /**** CORE ****/ -int __vsock_core_init(const stru...

...3f..b1c717286993 100644 > > --- a/include/net/af_vsock.h > > +++ b/include/net/af_vsock.h > > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > > /* Transport provides DGRAM communication */ > > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > > +/* Transport provides local (loopback) communication */ > > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > > > struct vsock_transport { > > struct module *module; > > diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c > &gt...

...t/af_vsock.h > > > > +++ b/include/net/af_vsock.h > > > > @@ -98,6 +98,8 @@ struct vsock_transport_send_notify_data { > > > > #define VSOCK_TRANSPORT_F_G2H 0x00000002 > > > > /* Transport provides DGRAM communication */ > > > > #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > > > > +/* Transport provides local (loopback) communication */ > > > > +#define VSOCK_TRANSPORT_F_LOCAL 0x00000008 > > > > > > > > struct vsock_transport { > > > > struct module *module; > > > > diff --git a/n...

...k/vmci_transport.c b/net/vmw_vsock/vmci_transport.c index 52e63952d0d4..900392686c03 100644 --- a/net/vmw_vsock/vmci_transport.c +++ b/net/vmw_vsock/vmci_transport.c @@ -2021,6 +2021,7 @@ static u32 vmci_transport_get_local_cid(void) static struct vsock_transport vmci_transport = { .features = VSOCK_TRANSPORT_F_DGRAM | VSOCK_TRANSPORT_F_H2G, + .module = THIS_MODULE, .init = vmci_transport_socket_init, .destruct = vmci_transport_destruct, .release = vmci_transport_release, -- 2.21.0

...id, .init = virtio_transport_do_socket_init, diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h index 27a3463e4892..269e2f034789 100644 --- a/include/net/af_vsock.h +++ b/include/net/af_vsock.h @@ -100,6 +100,8 @@ struct vsock_transport_send_notify_data { #define VSOCK_TRANSPORT_F_DGRAM 0x00000004 struct vsock_transport { + struct module *module; + /* Initialize/tear-down socket. */ int (*init)(struct vsock_sock *, struct vsock_sock *); void (*destruct)(struct vsock_sock *); diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c index dddd85d9a147..1f2e707cae66...

This series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use VSOCK with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using VMware

This series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use VSOCK with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using VMware

Most of the patches are reviewed by Dexuan, Stefan, and Jorgen. The following patches need reviews: - [11/15] vsock: add multi-transports support - [12/15] vsock/vmci: register vmci_transport only when VMCI guest/host are active - [15/15] vhost/vsock: refuse CID assigned to the guest->host transport RFC: https://patchwork.ozlabs.org/cover/1168442/ v1:

...*/ > +/* Transport provides host->guest communication */ > +#define VSOCK_TRANSPORT_F_H2G 0x00000001 > +/* Transport provides guest->host communication */ > +#define VSOCK_TRANSPORT_F_G2H 0x00000002 > +/* Transport provides DGRAM communication */ > +#define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > + > struct vsock_transport { > /* Initialize/tear-down socket. */ > int (*init)(struct vsock_sock *, struct vsock_sock *); > @@ -154,12 +162,8 @@ struct vsock_transport { > > /**** CORE ****/ > > -int __vsock_core_init(const s...

...*/ > +/* Transport provides host->guest communication */ > +#define VSOCK_TRANSPORT_F_H2G 0x00000001 > +/* Transport provides guest->host communication */ > +#define VSOCK_TRANSPORT_F_G2H 0x00000002 > +/* Transport provides DGRAM communication */ > +#define VSOCK_TRANSPORT_F_DGRAM 0x00000004 > + > struct vsock_transport { > /* Initialize/tear-down socket. */ > int (*init)(struct vsock_sock *, struct vsock_sock *); > @@ -154,12 +162,8 @@ struct vsock_transport { > > /**** CORE ****/ > > -int __vsock_core_init(const s...

Hi all, this series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using