search for: pr_devel

...dg->dst.context == VMCI_HYPERVISOR_CONTEXT_ID) + return VMCI_ERROR_DST_UNREACHABLE; + + ASSERT(dg->dst.context != VMCI_HYPERVISOR_CONTEXT_ID); + + /* Check that source handle matches sending context. */ + if (dg->src.context != contextID) { + pr_devel("Sender context (ID=0x%x) is not owner of src " \ + "datagram entry (handle=0x%x:0x%x).", + contextID, dg->src.context, dg->src.resource); + return VMCI_ERROR_NO_ACCESS; + } + + /* Get hold of privileg...

...dg->dst.context == VMCI_HYPERVISOR_CONTEXT_ID) + return VMCI_ERROR_DST_UNREACHABLE; + + ASSERT(dg->dst.context != VMCI_HYPERVISOR_CONTEXT_ID); + + /* Check that source handle matches sending context. */ + if (dg->src.context != contextID) { + pr_devel("Sender context (ID=0x%x) is not owner of src " \ + "datagram entry (handle=0x%x:0x%x).", + contextID, dg->src.context, dg->src.resource); + return VMCI_ERROR_NO_ACCESS; + } + + /* Get hold of privileg...

...uintptr_t eventHnd, + int userVersion, + const struct cred *cred, + struct vmci_ctx **outContext) +{ + struct vmci_ctx *context; + int result; + + if (privFlags & ~VMCI_PRIVILEGE_ALL_FLAGS) { + pr_devel("Invalid flag (flags=0x%x) for VMCI context.", + privFlags); + return VMCI_ERROR_INVALID_ARGS; + } + + if (userVersion == 0) + return VMCI_ERROR_INVALID_ARGS; + + context = kzalloc(sizeof(*context), GFP_KERNEL); +...

...uintptr_t eventHnd, + int userVersion, + const struct cred *cred, + struct vmci_ctx **outContext) +{ + struct vmci_ctx *context; + int result; + + if (privFlags & ~VMCI_PRIVILEGE_ALL_FLAGS) { + pr_devel("Invalid flag (flags=0x%x) for VMCI context.", + privFlags); + return VMCI_ERROR_INVALID_ARGS; + } + + if (userVersion == 0) + return VMCI_ERROR_INVALID_ARGS; + + context = kzalloc(sizeof(*context), GFP_KERNEL); +...

...ost_context_notify(uint32_t srcCID, + struct vmci_handle handle) +{ + struct dbell_entry *entry; + struct vmci_resource *resource; + int result; + + ASSERT(vmci_host_code_active()); + + if (VMCI_HANDLE_INVALID(handle)) { + pr_devel("Notifying an invalid doorbell " \ + "(handle=0x%x:0x%x).", handle.context, + handle.resource); + return VMCI_ERROR_INVALID_ARGS; + } + + resource = vmci_resource_get(handle, VMCI_RESOURCE_TYPE_DOORBELL); +...

...ost_context_notify(uint32_t srcCID, + struct vmci_handle handle) +{ + struct dbell_entry *entry; + struct vmci_resource *resource; + int result; + + ASSERT(vmci_host_code_active()); + + if (VMCI_HANDLE_INVALID(handle)) { + pr_devel("Notifying an invalid doorbell " \ + "(handle=0x%x:0x%x).", handle.context, + handle.resource); + return VMCI_ERROR_INVALID_ARGS; + } + + resource = vmci_resource_get(handle, VMCI_RESOURCE_TYPE_DOORBELL); +...

...cid_update(u32 subID, + struct vmci_event_data *eventData, + void *clientData) +{ + struct vmci_event_payld_ctx *evPayload = + vmci_event_data_payload(eventData); + + if (subID != ctxUpdateSubID) { + pr_devel("Invalid subscriber (ID=0x%x).", subID); + return; + } + + if (eventData == NULL || evPayload->contextID == VMCI_INVALID_ID) { + pr_devel("Invalid event data."); + return; + } + + pr_devel("Updating contex...

...cid_update(u32 subID, + struct vmci_event_data *eventData, + void *clientData) +{ + struct vmci_event_payld_ctx *evPayload = + vmci_event_data_payload(eventData); + + if (subID != ctxUpdateSubID) { + pr_devel("Invalid subscriber (ID=0x%x).", subID); + return; + } + + if (eventData == NULL || evPayload->contextID == VMCI_INVALID_ID) { + pr_devel("Invalid event data."); + return; + } + + pr_devel("Updating contex...

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

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

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

* * * 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

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.

...+ struct vmci_handle resourceHandle, + VMCIResourceFreeCB containerFreeCB, + void *containerObject) +{ + int result; + + ASSERT(resource); + + if (VMCI_HANDLE_EQUAL(resourceHandle, VMCI_INVALID_HANDLE)) { + pr_devel("Invalid argument resource (handle=0x%x:0x%x)", + resourceHandle.context, resourceHandle.resource); + return VMCI_ERROR_INVALID_ARGS; + } + + vmci_hash_init_entry(&resource->hashEntry, resourceHandle); + resource->type = res...

...+ struct vmci_handle resourceHandle, + VMCIResourceFreeCB containerFreeCB, + void *containerObject) +{ + int result; + + ASSERT(resource); + + if (VMCI_HANDLE_EQUAL(resourceHandle, VMCI_INVALID_HANDLE)) { + pr_devel("Invalid argument resource (handle=0x%x:0x%x)", + resourceHandle.context, resourceHandle.resource); + return VMCI_ERROR_INVALID_ARGS; + } + + vmci_hash_init_entry(&resource->hashEntry, resourceHandle); + resource->type = res...