System and method for coordinating process and memory management across domains

• US 10,394,602 B2
• Filed: 05/29/2014
• Issued: 08/27/2019
• Est. Priority Date: 05/29/2014
• Status: Active Grant

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: Singh, Ravi, Major, Daniel Jonas, Nagarajan, Sivakumar, Goodman, Kevin
• Primary Examiner(s): Wu, Benjamin C
• Assistant Examiner(s): Ayers, Michael W
• Application Number:
  US14/290,378
• Publication Number:
  US 20150347190A1
• Time in Patent Office: 1,916 Days
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

A method at a computing device having a plurality of concurrently operative operating systems, the method comprising: operating a proxy process within a target operating system on the computing device; receiving, from an originating operating system, a request for resources from a target process within the target operating system at the proxy process; requesting, from the proxy process, the resources of the target process; and returning a handle to the target process from the proxy process to the originating operating system.

Claims

1. A method at a computing device having a plurality of concurrently operative operating systems including an originating operating system, comprising at least one originating process, and a target operating system, comprising one or more resources, the method comprising:

operating a proxy process within the target operating system on the computing device, the proxy process being marked to avoid being shut down even if the target operating system is running low on memory;

receiving, by the proxy process, from the originating operating system, a first request for the at least one originating process to interact with a resource of the one or more resources from the target operating system, the first request including at least one process identifier identifying the at least one originating process, and a resource identifier that identifies the requested resource;

sending a second request, from the proxy process to the target operating system, for the resource;

determining, by the target operating system, that no process currently running within the target operating system provides access to the resource;

responsive to the determining, starting, by the target operating system, a target process;

providing access to the resource to the target process;

returning a handle to the target process from the proxy process to the originating operating system, the handle enabling the at least one originating process to interact directly with the target process within the target operating system to thereby interact with the resource, wherein the proxy process maintains an association between process identifiers of one or more processes external to the target operating system, including the at least one originating process, and resource identifiers of the one or more resources with which the external processes interact;

receiving, at the proxy process, from the at least one originating process in the originating operating system, an indication that the at least one originating process no longer interacts with the requested resource, the indication comprising the resource identifier;

receiving, at the target operating system, from the proxy process, an indication that the requested resource is no longer needed by the proxy process upon determining, based on the association maintained by the proxy process, that no process external to the target operating system interacts with the requested resource identified by the resource identifier; and

ending, by the target operating system, the target process.

2. The method of claim 1, further comprising populating a table within the proxy process with an identifier for the originating process within the originating operating system, an identifier for the originating operating system, and the resource identifier.

3. The method of claim 2, further comprising removing entries from the table when the originating process is finished with the resource.

4. The method of claim 3, further comprising informing the target operating system that the proxy process is finished with the resource if no entries in the table contain an identifier for the resource.

5. The method of claim 3, wherein the proxy process polls the originating operating system regarding a status of the originating process.

6. The method of claim 3, wherein the proxy process registers a trigger with the originating operating system to be informed when the originating process ends.

7. The method of claim 1, wherein the target process is a content provider.

8. A computing device having a plurality of concurrently operative operating systems including an originating operating system, comprising at least one originating process, and a target operating system, comprising one or more resources the computing device comprising:

a processor; and

memory,

wherein the computing device is configured to;

operate a proxy process within the target operating system on the computing device, the proxy process being marked to avoid being shut down even if the target operating system is running low on memory;

receive, by the proxy process, from the originating operating system, a first request for the at least one originating process to interact with a resource of the one or more resources from the target operating system, the first request including at least one process identifier identifying the at least one originating process, and a resource identifier that identifies the requested resource;

send a second request, from the proxy process to the target operating system, for the resource;

determine, by the target operating system, that no process currently running within the target operating system provides access to the resource;

responsive to the determining, start, by the target operating system, a target process, the target process holding the resource;

providing access to the resource to the target process;

return a handle to the target process from the proxy process to the originating operating system, the handle enabling the at least one originating process to interact directly with the target process within the target operating system to thereby interact with the resource, wherein the proxy process maintains an association between process identifiers of one or more processes external to the target operating system, including the at least one originating process, and resource identifiers of the one or more resources with which the external processes interact;

receive, at the proxy process, from the at least one originating process in the originating operating system, an indication that the at least one originating process no longer interacts with the requested resource, the indication comprising the resource identifier;

receive, at the target operating system, from the proxy process, an indication that the requested resource is no longer needed by the proxy process upon determining, based on the association maintained by the proxy process, that no process external to the target operating system interacts with the requested resource identified by the resource identifier; and

end, by the target operating system, the target process.

9. The computing device of claim 8, wherein the computing device is further configured to populate a table within the proxy process with an identifier for the originating process within the originating operating system, an identifier for the originating operating system, and the resource identifier.

10. The computing device of claim 9, wherein the computing device is further configured to remove entries from the table when the originating process is finished with the resource.

11. The computing device of claim 10, wherein the computing device is further configured to inform the target operating system that the proxy process is finished with the resource if no entries in the table contain an identifier for the resource.

12. The computing device of claim 10, wherein the proxy process polls the originating operating system regarding a status of the originating process.

13. The computing device of claim 10, wherein the proxy process registers a trigger with the originating operating system to be informed when the originating process ends.

14. The computing device of claim 8, wherein the target process is a content provider.

15. The computing device of claim 8, wherein the computing device is a mobile device.