search for: vmci_resource_release

...* Entry is freed in VMCIDatagram_DestroyHnd, who waits for + * the signal. + */ + wake_up(&entry->destroyEvent); +} + +static int dg_release_cb(void *clientData) +{ + struct datagram_entry *entry = (struct datagram_entry *)clientData; + ASSERT(entry); + vmci_resource_release(&entry->resource); + return 0; +} + +/* + * Create a datagram entry given a handle pointer. + */ +static int dg_create_handle(u32 resourceID, + u32 flags, + u32 privFlags, + vmci_datagram_recv_cb recvCB, +...

...* Entry is freed in VMCIDatagram_DestroyHnd, who waits for + * the signal. + */ + wake_up(&entry->destroyEvent); +} + +static int dg_release_cb(void *clientData) +{ + struct datagram_entry *entry = (struct datagram_entry *)clientData; + ASSERT(entry); + vmci_resource_release(&entry->resource); + return 0; +} + +/* + * Create a datagram entry given a handle pointer. + */ +static int dg_create_handle(u32 resourceID, + u32 flags, + u32 privFlags, + vmci_datagram_recv_cb recvCB, +...

...) +{ + struct dbell_entry *entry = (struct dbell_entry *)clientData; + ASSERT(entry); + wake_up(&entry->destroyEvent); +} + +static int dbell_release_cb(void *clientData) +{ + struct dbell_entry *entry = (struct dbell_entry *)clientData; + ASSERT(entry); + vmci_resource_release(&entry->resource); + return 0; +} + +/* + * Utility function that retrieves the privilege flags associated + * with a given doorbell handle. For guest endpoints, the + * privileges are determined by the context ID, but for host + * endpoints privileges are associated with the complete...

...) +{ + struct dbell_entry *entry = (struct dbell_entry *)clientData; + ASSERT(entry); + wake_up(&entry->destroyEvent); +} + +static int dbell_release_cb(void *clientData) +{ + struct dbell_entry *entry = (struct dbell_entry *)clientData; + ASSERT(entry); + vmci_resource_release(&entry->resource); + return 0; +} + +/* + * Utility function that retrieves the privilege flags associated + * with a given doorbell handle. For guest endpoints, the + * privileges are determined by the context ID, but for host + * endpoints privileges are associated with the complete...

...eType) +{ + struct vmci_resource *resource = + vmci_resource_get(resourceHandle, resourceType); + + if (resource == NULL) + return; + + /* Remove resource from hashtable. */ + vmci_hash_remove(resourceTable, &resource->hashEntry); + + vmci_resource_release(resource); + /* resource could be freed by now. */ +} + +struct vmci_resource *vmci_resource_get(struct vmci_handle resourceHandle, + enum vmci_resource_type resourceType) +{ + struct vmci_resource *resource; + struct vmci_hash_entry *entry =...

...eType) +{ + struct vmci_resource *resource = + vmci_resource_get(resourceHandle, resourceType); + + if (resource == NULL) + return; + + /* Remove resource from hashtable. */ + vmci_hash_remove(resourceTable, &resource->hashEntry); + + vmci_resource_release(resource); + /* resource could be freed by now. */ +} + +struct vmci_resource *vmci_resource_get(struct vmci_handle resourceHandle, + enum vmci_resource_type resourceType) +{ + struct vmci_resource *resource; + struct vmci_hash_entry *entry =...

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.