search for: vsock_core_unregister

...gt; + goto err_busy; > + } > + t_local = t; > + } > + > transport_h2g = t_h2g; > transport_g2h = t_g2h; > transport_dgram = t_dgram; > + transport_local = t_local; > > err_busy: > mutex_unlock(&vsock_register_mutex); > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > vsock_transport *t) > if (transport_dgram == t) > transport_dgram = NULL; > > + if (transport_local == t) > + transport_local = NULL; > + > mutex_unlock(&vsock_register_mutex); > } > EXPORT_SYMBOL_GPL(vsock_core_unregister); > -- > 2...

...gt; + goto err_busy; > + } > + t_local = t; > + } > + > transport_h2g = t_h2g; > transport_g2h = t_g2h; > transport_dgram = t_dgram; > + transport_local = t_local; > > err_busy: > mutex_unlock(&vsock_register_mutex); > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > vsock_transport *t) > if (transport_dgram == t) > transport_dgram = NULL; > > + if (transport_local == t) > + transport_local = NULL; > + > mutex_unlock(&vsock_register_mutex); > } > EXPORT_SYMBOL_GPL(vsock_core_unregister); > -- > 2...

...> transport_h2g = t_h2g; > > > transport_g2h = t_g2h; > > > transport_dgram = t_dgram; > > > + transport_local = t_local; > > > > > > err_busy: > > > mutex_unlock(&vsock_register_mutex); > > > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > > > vsock_transport *t) > > > if (transport_dgram == t) > > > transport_dgram = NULL; > > > > > > + if (transport_local == t) > > > + transport_local = NULL; > > > + > > > mutex_unlock(&vsock_register...

...> transport_h2g = t_h2g; > > > transport_g2h = t_g2h; > > > transport_dgram = t_dgram; > > > + transport_local = t_local; > > > > > > err_busy: > > > mutex_unlock(&vsock_register_mutex); > > > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > > > vsock_transport *t) > > > if (transport_dgram == t) > > > transport_dgram = NULL; > > > > > > + if (transport_local == t) > > > + transport_local = NULL; > > > + > > > mutex_unlock(&vsock_register...

...se vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Major changes: - vsock core module can be loaded regardless of the transports - vsock_core_init() and vsock_core_exit() are renamed to vsock_core_register() and vsock_core_unregister() - vsock_core_register() has a feature parameter (H2G, G2H, DGRAM) to identify which directions the transport can handle and if it's support DGRAM (only vmci) - each stream socket is assigned to a transport when the remote CID is set (during the connect() or when we receive a connection...

...rdependently of the transports - each 'struct virtio_transport' has a new feature fields (H2G, G2H, DGRAM) to identify which directions the transport can handle and if it's support DGRAM (only vmci) - vsock_core_init() and vsock_core_exit() are renamed to vsock_core_register() and vsock_core_unregister() - each stream socket is assigned to a transport when the remote CID is set (during the connect() or when we receive a connection request on a listener socket). The remote CID is used to decide which transport to use: - remote CID > VMADDR_CID_HOST will use host->guest transport -...

...t; > > + } > > + > > transport_h2g = t_h2g; > > transport_g2h = t_g2h; > > transport_dgram = t_dgram; > > + transport_local = t_local; > > > > err_busy: > > mutex_unlock(&vsock_register_mutex); > > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > > vsock_transport *t) > > if (transport_dgram == t) > > transport_dgram = NULL; > > > > + if (transport_local == t) > > + transport_local = NULL; > > + > > mutex_unlock(&vsock_register_mutex); > > } > > EXPORT...

...> > > transport_g2h = t_g2h; > > > > transport_dgram = t_dgram; > > > > + transport_local = t_local; > > > > > > > > err_busy: > > > > mutex_unlock(&vsock_register_mutex); > > > > @@ -2187,6 +2199,9 @@ void vsock_core_unregister(const struct > > > > vsock_transport *t) > > > > if (transport_dgram == t) > > > > transport_dgram = NULL; > > > > > > > > + if (transport_local == t) > > > > + transport_local = NULL; > > > > + > > >...

...ng also different hypervisors) loading both guest->host and > host->guest transports at the same time. > > Major changes: > - vsock core module can be loaded regardless of the transports > - vsock_core_init() and vsock_core_exit() are renamed to > vsock_core_register() and vsock_core_unregister() > - vsock_core_register() has a feature parameter (H2G, G2H, DGRAM) > to identify which directions the transport can handle and if it's > support DGRAM (only vmci) > - each stream socket is assigned to a transport when the remote CID > is set (during the connect() or when...

...ng also different hypervisors) loading both guest->host and > host->guest transports at the same time. > > Major changes: > - vsock core module can be loaded regardless of the transports > - vsock_core_init() and vsock_core_exit() are renamed to > vsock_core_register() and vsock_core_unregister() > - vsock_core_register() has a feature parameter (H2G, G2H, DGRAM) > to identify which directions the transport can handle and if it's > support DGRAM (only vmci) > - each stream socket is assigned to a transport when the remote CID > is set (during the connect() or when...

...4,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 unregistration > + */ If unregister() is only called from module_exit() functions...

...NULL, &vmci_transport_qp_resumed_sub_id); @@ -2094,8 +2096,14 @@ static int __init vmci_transport_init(void) if (err < 0) goto err_unsubscribe; + err = vmci_register_vsock_callback(vmci_vsock_transport_cb); + if (err < 0) + goto err_unregister; + return 0; +err_unregister: + vsock_core_unregister(&vmci_transport); err_unsubscribe: vmci_event_unsubscribe(vmci_transport_qp_resumed_sub_id); err_destroy_stream_handle: @@ -2121,6 +2129,7 @@ static void __exit vmci_transport_exit(void) vmci_transport_qp_resumed_sub_id = VMCI_INVALID_ID; } + vmci_register_vsock_callback(NULL); vso...

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

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

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:

v2: - style fixes [Dave] - removed RCU sync and changed 'the_vsock_loopback' in a global static variable [Stefan] - use G2H transport when local transport is not loaded and remote cid is VMADDR_CID_LOCAL [Stefan] - rebased on net-next v1: https://patchwork.kernel.org/cover/11251735/ This series introduces a new transport (vsock_loopback) to handle local communication. This

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

...; also different hypervisors) loading both guest->host and > host->guest transports at the same time. > > Major changes: > - vsock core module can be loaded regardless of the transports > - vsock_core_init() and vsock_core_exit() are renamed to > vsock_core_register() and vsock_core_unregister() > - vsock_core_register() has a feature parameter (H2G, G2H, DGRAM) > to identify which directions the transport can handle and if it's > support DGRAM (only vmci) > - each stream socket is assigned to a transport when the remote CID > is set (during the connect() or when...

...; also different hypervisors) loading both guest->host and > host->guest transports at the same time. > > Major changes: > - vsock core module can be loaded regardless of the transports > - vsock_core_init() and vsock_core_exit() are renamed to > vsock_core_register() and vsock_core_unregister() > - vsock_core_register() has a feature parameter (H2G, G2H, DGRAM) > to identify which directions the transport can handle and if it's > support DGRAM (only vmci) > - each stream socket is assigned to a transport when the remote CID > is set (during the connect() or when...