search for: vmci_host_vsock_load

...; > > Since we don't unregister the transport if user count drops back to 0, we > could > > just call this the first time, a VM is powered on after the module is loaded. > > Yes, make sense. can I use the 'vmci_host_active_users' or is better to > add a new 'vmci_host_vsock_loaded'? > > My doubt is that vmci_host_active_users can return to 0, so when it returns > to 1, we call vmci_call_vsock_callback() again. vmci_host_active_users can drop to 0 and then increase again, so having a flag indicating whether the callback has been invoked would ensure that it i...

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Wednesday, October 23, 2019 11:56 AM > > To allow other transports to be loaded with vmci_transport, > we register the vmci_transport as G2H or H2G only when a VMCI guest > or host is active. > > To do that, this patch adds a callback registered in the vmci driver > that will be called when a new host

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Wednesday, October 23, 2019 11:56 AM > > To allow other transports to be loaded with vmci_transport, > we register the vmci_transport as G2H or H2G only when a VMCI guest > or host is active. > > To do that, this patch adds a callback registered in the vmci driver > that will be called when a new host

...llback(true); > > + > > Since we don't unregister the transport if user count drops back to 0, we could > just call this the first time, a VM is powered on after the module is loaded. Yes, make sense. can I use the 'vmci_host_active_users' or is better to add a new 'vmci_host_vsock_loaded'? My doubt is that vmci_host_active_users can return to 0, so when it returns to 1, we call vmci_call_vsock_callback() again. Thanks, Stefano