Homogeneous Programming For Heterogeneous Multiprocessor Systems

• US 20080244507A1
• Filed: 03/30/2007
• Published: 10/02/2008
• Est. Priority Date: 03/30/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hunt, Galen C., Hodson, Orion, Gunawi, Haryadi
• Application Number:
  US11/694,455
• Publication Number:
  US 20080244507A1
• Time in Patent Office: Days
• US Class Current: 717/106
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space

Abstract

Systems and methods establish communication and control between various heterogeneous processors in a computing system so that an operating system can run an application across multiple heterogeneous processors. With a single set of development tools, software developers can create applications that will flexibly run on one CPU or on combinations of central, auxiliary, and peripheral processors. In a computing system, application-only processors can be assigned a lean subordinate kernel to manage local resources. An application binary interface (ABI) shim is loaded with application binary images to direct kernel ABI calls to a local subordinate kernel or to the main OS kernel depending on which kernel manifestation is controlling requested resources.

Claims

1. A method, comprising:

receiving a software application;

coding the software application to run on multiple heterogeneous processors of a computing system;

wherein the coded software application is capable of;

running only on a main processor of the computing system;

running only on one or more auxiliary processors of the computing system; and

running on a combination of the main processor and one or more of the auxiliary processors.

2. The method as recited in claim 1, wherein coding the software application includes:

parsing a manifest;

creating a list of resources utilized by the software application; and

creating application code;

wherein the manifest describes resources that the software application requests via the operating system, dependencies of the software application on components of the computing system, and resources provided by the software application.

3. The method as recited in claim 1, wherein coding the software application includes coding for compatibility with an operating system that performs services, including:

establishing communication between the processors for managing computing resources associated with each processor;

installing the software application; and

allocating processes of the software application among the computing resources of the processors.

4. The method as recited in claim 3, wherein coding the software application includes coding in architecture independent code, including one of an intermediate language or a byte code.

5. The method as recited in claim 3, wherein the installing includes verifying a type safety and a memory safety of an architecture independent code.

6. The method as recited in claim 3, wherein the installing includes:

invoking a code compiler;

configuring a tool chain for transforming an architecture independent code into application binary images that target specific instruction set architectures of the processors that will run the software application; and

wherein the application binary images are based on a manifest and based on properties of an instruction stream.

7. The method as recited in claim 6, wherein the transforming further includes:

generating the application binary images from the architecture independent code, an application runtime library, one or more standard libraries of routines that support the software application; and

creating a kernel application binary interface (ABI) shim.

8. The method as recited in claim 7, wherein the kernel ABI shim comprises a library that is compiled into the application binary image or that is dynamically loaded when the software application starts.

9. The method as recited in claim 7, wherein the kernel ABI shim exports a kernel ABI and handles requests to the operating system.

10. The method as recited in claim 9, wherein the processors of the computing system include a main processor and one or more auxiliary processors;

wherein the operating system runs on a first subset of the processors that includes the main processor, and the processes of the software application run on one or more additional subsets of the processors; and

wherein the transforming creates at least one kernel ABI shim for each different subset of processors running processes of the software application.

11. The method as recited in claim 10, further comprising running a subordinate kernel agent on each of the additional subsets of processors as a software agent of the operating system;

and

wherein each subordinate kernel agent manages computing resources and a memory of the associated subset of processors and is capable of thread scheduling on behalf of the associated subset of processors.

12. The method as recited in claim 11, wherein:

for a process of the software application running on the first subset of processors that runs the operating system;

when the process makes a kernel ABI call, the process or the corresponding ABI shim calls directly to an operating system kernel; and

for a process of the software application running only on one of the additional subsets of processors;

when the process makes a kernel ABI call, the corresponding ABI shim;

calls to a local subordinate kernel when the ABI call relates to resources managed by the subordinate kernel; and

performs remote method invocations on the first subset of processors running the operating system when the ABI call relates to resources not managed by the local subordinate kernel.

13. The method as recited in claim 11, wherein the processes of the software application communicate with each other via a bidirectional channel.

14. The method as recited in claim 13, further comprising invoking a remote method to enable two of the processes to communicate with each other when each of the two processes run on separate additional subsets that of processors that do not run the operating system.

15. The method as recited in claim 14, further comprising resolving lower level transport settings, methods, and arguments of a call via a resolver protocol executed by an intermediating processor.

16. The method as recited in claim 13, wherein processes of the software application running on different processors are protected from each other via type safety and memory safety properties and via limiting each process to communicating only through the kernel ABI shim and through the bidirectional channel.

17. The method as recited in claim 13, wherein the bidirectional channel has only two endpoints;

wherein a type and sequence of messages exchangeable between the two endpoints is declared in a channel contract; and

wherein the operating system starts each process with an initial set of channel endpoints, and each process can only communicate with other processes holding one of the channel endpoints.

18. The method as recited in claim 17, wherein a message has associated arguments;

and

wherein allowed instances of the associated arguments include;

value types, linear data pointers, data structures composed of both value types and linear data pointers, and pointers into a memory address space of a sending process.

19. The method as recited in claim 9, wherein the kernel ABI shim is indistinguishable from the kernel ABI to a running process of the software application.

20. The method as recited in claim 9, wherein a single source code enables the software application to run on the first subset of processors running the operating system or on one or more of the additional subsets of processors.