VM inter-process communication

• US 10,268,597 B2
• Filed: 04/06/2018
• Issued: 04/23/2019
• Est. Priority Date: 11/16/2007
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Wibling, Gustav Seth, Krishnan, Jagannath Gopal
• Primary Examiner(s): Tsai, Sheng Jen
• Application Number:
  US15/947,712
• Publication Number:
  US 20180232315A1
• Time in Patent Office: 382 Days
• Field of Search: 711147
• CPC Class Codes: G06F 12/109 for multiple virtual address spaces, e.g. segmentation G06F12/1036 takes precedence
• CPC Class Codes: G06F 2212/1008 Correctness of operation, e.g. memory ordering
• CPC Class Codes: G06F 2212/152 Virtualized environment, e.g. logically partitioned system
• CPC Class Codes: G06F 2212/656 Address space sharing
• CPC Class Codes: G06F 2212/657 Virtual address space management
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A method is described for enabling inter-process communication between a first application and a second application, the first application running within a first virtual machine (VM) in a host and the second application running within a second VM in the host, The method includes receiving a request to attach a shared region of memory to a memory allocation, identifying a list of one or more physical memory pages defining the shared region that corresponds to the handle, and mapping guest memory pages corresponding to the allocation to the physical memory pages. The request may be received by a framework from the second application and includes a handle that uniquely identifies the shared region of memory as well as an identification of at least one guest memory page corresponding to the memory allocation.

Claims

1. A method for enabling inter-process communication between a first application and a second application, the first application running within a first virtual machine (VM) in a host and the second application running within a second VM in the host, the method comprising:

creating a shared memory region in physical memory for access during execution of the first application, the shared memory region being associated with a handle and being mapped to guest memory of the first VM, the guest memory of the first VM being virtualized memory of the physical memory of the host for the first VM;

enabling discovery of the presence of the shared memory region and the handle associated with the shared memory region for purposes of use by the second application;

in response to the second application discovering the presence of the shared memory region, attaching the shared region of memory to guest memory of the second VM for access during execution of the second application, the guest memory of the second VM being virtualized memory of the physical memory of the host, the attaching being based on the handle that uniquely identifies the shared region of memory and being executed by a framework that is a component of virtualization software in the host;

identifying a first list of physical memory pages in the physical memory as a first portion of the shared memory region that corresponds to the guest memory of the first VM;

identifying a second list of physical memory pages in the physical memory as a second portion of the shared memory region that corresponds to the guest memory of the second VM; and

mapping a portion of the guest memory of the second VM to the shared memory region in the physical memory.

2. The method of claim 1, wherein creating the shared memory region includes binding the handle uniquely identifying the shared memory region with an identifier that is available to both the first application and the second application.

3. The method of claim 2, further comprising:

receiving a handle request for the handle associated with the shared memory region from the second application at the framework, the handle request including the identifier for the shared memory region;

in response to the handle request, accessing a registry to locate the handle associated with the identifier included in the handle request; and

returning the handle to the second application to indicate the presence of the shared memory region.

4. The method of claim 3, wherein the handle request is received through a hypercall, which is a call made from a VM to the virtualization software.

5. The method of claim 3, further comprising:

receiving a size request for the size of the shared memory region from the second application at the framework, the size request including the handle; and

in response to the size request, returning the size of the shared memory region to the second application.

6. The method of claim 5, wherein the size request is received through a hypercall, which is a call made from a VM to the virtualization software.

7. The method of claim 1, wherein identifying the first list of physical pages includes accessing a registry.

8. The method of claim 1, further comprising:

receiving a request from the first application to create the shared memory region at the framework, the request including an identification of a plurality of pages of virtualized guest memory;

identifying one or more physical pages of the physical memory that correspond with a list of virtualized guest memory pages provided with the request, the one or more physical pages defining the shared memory region;

creating the handle; and

returning the handle to the first application.

10. The non-transitory computer-readable medium of claim 1, wherein creating the shared memory region includes binding the handle uniquely identifying the shared memory region with an identifier that is available to both the first application and the second application.

11. The non-transitory computer-readable medium of claim 10, wherein the method further comprises:

receiving a handle request for the handle associated with the shared memory region from the second application at the framework, the handle request including the identifier for the shared memory region;

in response to the handle request, accessing a registry to locate the handle associated with the identifier included in the handle request; and

returning the handle to the second application to indicate the presence of the shared memory region.

12. The non-transitory computer-readable medium of claim 11, wherein the handle request is received through a hypercall, which is a call made from a VM to the virtualization software.

13. The non-transitory computer-readable medium of claim 11, wherein the method further comprises:

receiving a size request for the size of the shared memory region from the second application at the framework, the size request including the handle; and

in response to the size request, returning the size of the shared memory region to the second application.

14. The non-transitory computer-readable medium of claim 13, wherein the size request is received through a hypercall, which is a call made from a VM to the virtualization software.

9. A non-transitory computer-readable medium embodying program instructions for causing a computer to perform a method for enabling inter-process communication between a first application and a second application, the first application running within a first virtual machine (VM) in a host and the second application running within a second VM in the host, the method comprising:

creating a shared memory region in physical memory for access during execution of the first application, the shared memory region being associated with a handle and being mapped to guest memory of the first VM, the guest memory of the first VM being virtualized memory of the physical memory of the host for the first VM;

enabling discovery of the presence of the shared memory region and the handle associated with the shared memory region for purposes of use by the second application;

in response to the second application discovering the presence of the shared memory region, attaching the shared region of memory to guest memory of the second VM for access during execution of the second application, the guest memory of the second VM being virtualized memory of the physical memory of the host, the attaching being based on the handle that uniquely identifies the shared region of memory and being executed by a framework that is a component of virtualization software in the host;

identifying a first list of physical memory pages in the physical memory as a first portion of the shared memory region that corresponds to the guest memory of the first VM;

identifying a second list of physical memory pages in the physical memory as a second portion of the shared memory region that corresponds to the guest memory of the second VM; and

mapping a portion of the guest memory of the second VM to the shared memory region in the physical memory.

15. The non-transitory computer-readable medium of claim 9, wherein identifying the first list of physical pages includes accessing a registry.

16. The non-transitory computer-readable medium of claim 9, wherein the method further comprises:

receiving a request from the first application to create the shared memory region at the framework, the request including an identification of a plurality of pages of virtualized guest memory;

identifying one or more physical pages of the physical memory that correspond with a list of virtualized guest memory pages provided with the request, the one or more physical pages defining the shared memory region;

creating the handle; and

returning the handle to the first application.

17. A host computer comprising:

physical memory; and

at least one processor configured to;

create a shared memory region in the physical memory for access during execution of a first application running within a first virtual machine (VM) in the host computer, the shared memory region being associated with a handle and being mapped to guest memory of the first VM, the guest memory of the first VM being virtualized memory of the physical memory of the host for the first VM;

enable discovery of the presence of the shared memory region and the handle associated with the shared memory region for purposes of use by a second application running within a second VM in the host computer;

in response to the second application discovering the presence of the shared memory region, attach the shared region of memory to guest memory of the second VM for access during execution of the second application, the guest memory of the second VM being virtualized memory of the physical memory of the host computer, a process of attaching the shared region of memory to the guest memory of the second VM being based on the handle that uniquely identifies the shared region of memory and being executed by a framework that is a component of virtualization software in the host computer;

identify a first list of physical memory pages in the physical memory as a first portion of the shared memory region that corresponds to the guest memory of the first VM;

identify a second list of physical memory pages in the physical memory as a second portion of the shared memory region that corresponds to the guest memory of the second VM; and

map a portion of the guest memory of the second VM to the shared memory region in the physical memory.

18. The host computer of claim 17, wherein the at least one processor is configured to bind the handle uniquely identifying the shared memory region with an identifier that is available to both the first application and the second application.

19. The host computer of claim 18, wherein the at least one processor is further configured to:

receive a handle request for the handle associated with the shared memory region from the second application at the framework, the handle request including the identifier for the shared memory region;

in response to the handle request, access a registry to locate the handle associated with the identifier included in the handle request; and

return the handle to the second application to indicate the presence of the shared memory region.

20. The host computer of claim 19, wherein the handle request is received through a hypercall, which is a call made from a VM to the virtualization software.