Power Profiling for Embedded System Design

• US 20110016455A1
• Filed: 01/31/2010
• Published: 01/20/2011
• Est. Priority Date: 07/20/2009
• Status: Abandoned Application

• Current Assignee: Glenn Perry, Herbert Yuen, Manfred Kreutzer, Thomas Gatterweh
• Original Assignee: Glenn Perry, Herbert Yuen, Manfred Kreutzer, Thomas Gatterweh
• Inventors: Gatterweh, Thomas, Kreutzer, Manfred, Perry, Glenn, Yuen, Herbert
• Application Number:
  US12/697,291
• Publication Number:
  US 20110016455A1
• Time in Patent Office: Days
• US Class Current: 717/130
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The power usage of software executable by an embedded system may be profiled without the need for test benches or power measurement systems. Additionally, the power profiles corresponding to multiple pieces of software may be determined and compared.

Claims

1. A computer-implemented method for generating a power profile for a computer executable application, the method comprising:

identifying a computer executable application;

traversing the computer executable application, the traversing generating a plurality of power consumption metrics;

generating a power profile for the computer executable application based in part upon the plurality of power consumption metrics; and

storing the power profile to a memory storage location.

2. The computer-implemented method recited in claim 1, the method further comprising displaying the power consumption profile for a user of the method.

3. A computer-implemented method for generating a power profile for a computer executable application, the method comprising:

identifying a computer executable application;

identifying a power specification corresponding to the computer executable application;

causing the computer executable application to be executed;

recording a plurality of power consumption metrics based in part upon the execution of the computer executable application;

generating a power profile for the computer executable application based in part upon the plurality of power consumption metrics and the power specification; and

storing the power profile to a memory storage location.

4. The computer-implemented method recited in claim 3, the method further comprising:

inserting one or more power profiling operations into the computer executable application; and

wherein

the method act for causing the computer executable application to be executed additionally causes the one or more power profiling operations to be executed.

5. The computer-implemented method recited in claim 4, wherein the method act of causing the computer executable application to be executed comprises:

identifying an embedded system environment;

causing the computer executable application to be executed by the embedded system environment;

causing the one or more power profiling operations to be executed by the embedded system environment, the one or more power profiling operations generating one or more power consumption metrics; and

identifying the one or more power consumption metrics.

6. The method recited in claim 5, wherein:

the method act of causing the computer executable application to be executed causes a plurality of instructions to be invoked;

a one of the one or more power profiling operations comprises counting the number of times the plurality of instructions are invoked; and

a one of the plurality of power consumption metrics is the number of time the plurality of instructions are invoked.

7. The method recited in claim 6, wherein:

the computer executable application includes a plurality of functions, each function causing one or more of the plurality of instructions to be invoked;

a one of the one or more power profiling operations comprises counting the number instructions invoked each time a one of the plurality of functions is invoked; and

a one of the plurality of power consumption metrics is the number instructions invoked each time the functions are called.

8. The method recited in claim 7, wherein:

ones of the plurality of instructions are memory access instructions;

for the ones of the plurality of instructions that are memory access instructions, determining the type of memory access instruction;

a one of the one or more power profiling operations comprises counting the number of times each type of memory access instruction is invoked; and

a one of the plurality of power consumption metrics is the number of time the ones of the plurality of instructions that are memory access instructions are invoked.

9. The method recited in claim 7, the method act of generating a power profile for the computer executable application comprising:

for each one of the plurality of power consumption metrics, identifying a corresponding unit of power consumed based upon the specification; and

deriving an amount of power consumed for the computer executable application based in part upon the plurality of power consumption metrics and the unit of power consumed.

10. A computer program product for generating a power profile for a computer executable application comprising:

software instructions for enabling a computer to perform a set of operations; and

one or more tangible computer-readable media bearing the software instructions;

the set of operations including;

identifying a computer executable application;

identifying a power specification corresponding to the computer executable application;

traversing the computer executable application, the traversing generating in a plurality of power consumption metrics;

generating a power profile for the computer executable application based in part upon the plurality of power consumption metrics and the power specification; and

storing the power profile to a memory storage location.

11. The computer program product recited in claim 10, the operation for traversing the computer executable application comprises causing the computer executable application to be executed.

12. The computer program product recited in claim 11, the set of operations further comprising:

inserting one or more power profiling operations into the computer executable application; and

wherein

the operation for traversing the computer executable application additionally traverses the one or more power profiling operations.

13. The computer program product in claim 12, the operation for causing the computer executable application to be executed comprises:

identifying an embedded system environment;

making the computer executable application available to the embedded system environment;

causing the embedded system environment to execute the computer executable application including the one or more power profiling operations, the execution of the one or more power profiling operations outputting one or more power consumption metrics; and

identifying the one or more power consumption metrics.

14. The computer program product recited in claim 13, wherein:

the computer executable application includes a plurality of instructions;

the method act of causing the embedded system environment to execute the computer executable application results in the plurality of instructions to being invoked;

a one of the one or more power profiling operations comprises counting the number of times the plurality of instructions are invoked; and

a one of the plurality of power consumption metrics is the number of time the plurality of instructions are invoked.

15. The computer program product recited in claim 14, wherein:

the computer executable application further includes a plurality of functions, each function including ones of the plurality of instructions;

a one of the one or more power profiling operations comprises counting the number of instructions invoked each time the plurality of functions are invoked; and

a one of the plurality of power consumption metrics is the number instructions invoked each time the plurality of functions are invoked.

16. The computer program product recited in claim 15, wherein:

ones of the plurality of instructions are memory access instructions;

for the ones of the plurality of instructions that are memory access instructions, determining the type of memory access instruction;

a one of the one or more power profiling operations comprises counting the number of times each type of memory access instruction is invoked; and

a one of the plurality of power consumption metrics is the number of time the ones of the plurality of instructions that are memory access instructions are invoked.

17. The computer program product recited in claim 16, wherein:

the power specification defines an amount of power consumed corresponding to each of the plurality of power consumption metrics; and

the operation for generating a power profile for the computer executable application comprises;

deriving an amount of power consumed for each for each one of the plurality of power consumption metrics, identifying a corresponding unit of power consumed based upon the specification; and

deriving an amount of power consumed for the computer executable application based in part upon the plurality of power consumption metrics and the unit of power consumed.

18. The computer program product recited in claim 14, wherein:

ones of the plurality of instructions are memory access instructions;

a one of the one or more power profiling operations comprises counting the number of times the ones of the plurality of instructions that are memory access instructions are invoked; and

a one of the power consumption metrics is the number of time the ones of the plurality of instructions that are memory access instructions are invoked.