SYSTEM AND METHOD FOR COORDINATING PROCESS AND MEMORY MANAGEMENT ACROSS DOMAINS

• US 20150347190A1
• Filed: 05/29/2014
• Published: 12/03/2015
• Est. Priority Date: 05/29/2014
• Status: Active Grant

• Current Assignee: Blackberry Limited
• Original Assignee: 2236008 Ontario Inc. (Blackberry Limited), Blackberry Limited
• Inventors: SINGH, Ravi, MAJOR, Daniel Jonas, NAGARAJAN, Sivakumar, GOODMAN, Kevin
• Granted Patent: US 10,394,602 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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, 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.

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

3. The method of claim 2, further comprising removing entries from the table when an 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 resource if no entries in the table contain an identifier for the resource.

5. The method of claim 3, wherein the originating process signals to the proxy process when it is finished with the resource.

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

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

8. The method of claim 1, wherein the proxy process is marked to not be shut down even if the target operating system is running low on memory.

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

10. A computing device having a plurality of concurrently operative operating systems, the computing device comprising:

a processor; and

memory,

wherein the computing device is configured to;

operate a proxy process within a target operating system on the computing device;

receive, from an originating operating system, a request for resources from a target process within the target operating system at the proxy process;

request, from the proxy process, the resources of the target process; and

return a handle to the target process from the proxy process to the originating operating system.

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

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

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

14. The computing device of claim 12, wherein the originating process signals to the proxy process when it is finished with the resource.

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

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

17. The computing device of claim 10, wherein the proxy process is marked to not be shut down even if the target operating system is running low on memory.

18. The computing device of claim 10, wherein the target process is a content provider.

19. The computing device of claim 10, wherein the computing device is a mobile device.