Method for firmware to provide seamless regulation of system resources and extend additional configuration methods for system resource management

• US 7,134,125 B2
• Filed: 02/07/2003
• Issued: 11/07/2006
• Est. Priority Date: 02/07/2003
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Zimmer, Vincent J., Rothman, Michael A.
• Primary Examiner(s): Thomson, William
• Assistant Examiner(s): CAO, DIEM K
• Application Number:
  US10/360,445
• Publication Number:
  US 20040158840A1
• Time in Patent Office: 1,369 Days
• Field of Search: 718/1, 718100-108, 719310-330
• US Class Current: 719/321
• CPC Class Codes: G06F 2209/504 Resource capping
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A method of system resource management. The method including: determining a class of a device agent and determining whether the device agent is requesting a controlled system resource or a non-controlled system resource. If a controlled system resource is requested by the device agent, then the method further includes determining whether a first amount of the controlled system resource requested by the device agent plus a second amount of the controlled system resource currently consumed by the class of the device agent, if any, together exceed a class allocation amount for the controlled system resource that is permissible for the class of the device agent to consume.

Claims

1. A machine-readable medium having instructions embodied thereon, the instructions to be executed by a machine to perform:

determining a class of a device agent requesting to use a first amount of a system resource of a processing system;

determining via a firmware agent whether the first amount of the system resource requested by the device agent plus a second amount of the system resource currently consumed by the class, if any, together exceed a class allocation amount of the system resource that is permissible for the class of the device agent to consume; and

controlling access to the system resource via the firmware agent during a pre-boot runtime of the processing system, wherein controlling access includes granting the device agent access to the system resource if the first amount plus the second amount do not exceed the class allocation amount.

2. The machine-readable medium of claim 1, wherein controlling access further includes denying the device agent access to the system resource if the first amount plus the second amount exceed the class allocation amount.

3. The machine-readable medium of claim 1 wherein the system resource is non-volatile memory.

4. The machine-readable medium of claim 1 wherein determining whether the first amount of the system resource requested by the device agent exceeds a class allocation amount includes referring to a resource configuration (“

RC”

) matrix correlating the system resource with the class allocation amount for the class of the device agent.

5. The machine-readable medium of claim 4 wherein the class allocation amount of the system resource comprises a ratio of the system resource.

6. The machine-readable medium of claim 1, further comprising:

executing the agent during the pre-boot runtime and during an operating system (“

OS”

) runtime of the processing system; and

controlling access to the system resource via the agent during the OS runtime.

7. A method of system resource management, comprising:

determining a class of a device agent;

determining whether a controlled system resource of a processing system or a non-controlled system resource of the processing system is requested by the device agent;

if a controlled system resource is requested, then determining whether a first amount of the controlled system resource requested by the device agent plus a second amount of the controlled system resource currently consumed by the class, if any, together exceed a class allocation amount for the controlled system resource that is permissible for the class of the device agent to consume; and

controlling access to the controlled system resource via a firmware agent

during a pre-boot runtime of the processing system, wherein the controlled system resource comprises any resource over which the firmware agent has control, and wherein controlling access includes granting the device agent access to the controlled system resource if the first amount plus the second amount do not exceed the class allocation amount.

8. The method of claim 7, wherein controlling access to the controlled system resource comprises:

denying the device agent access to the requested controlled system resource, if the first amount plus the second amount, if any, of the controlled system resource together exceed the class allocation amount.

9. The method of claim 8, further comprising:

returning an error message to the device agent, if the device agent is denied access to the requested controlled system resource.

10. The method of claim 8, further comprising:

storing an error message in an error log repository, if the device agent is denied access to the requested controlled system resource.

11. The method of claim 7, wherein controlling access to the controlled system resource comprises:

granting the device agent access to only an unconsumed amount of the controlled system resource permissible for the class of the device agent to consume, if the first amount plus the second amount, if any, of the controlled system resource together exceed the class allocation amount.

12. The method of claim 7, further comprising:

granting access to the non-controlled system resource, if a non-controlled system resource is requested by the device agent.

13. The method of claim 7 wherein the controlled system resource comprises non-volatile memory.

14. The method of claim 7 wherein the class allocation amount comprises a ratio of a total available amount of the controlled system resource.

15. The method of claim 7 wherein the class allocation amount comprises a fixed amount of the controlled system resource.

16. The method of claim 7 further comprising:

executing the agent during the pre-boot runtime and during an operating system (“

OS”

) runtime of the processing system; and

controlling access to the controlled system resource via the agent during the OS runtime.

17. A processing system, comprising:

a firmware memory device to store instructions therein; and

a central processing unit (“

CPU”

) coupled to receive the instructions from the firmware memory device, the instructions to selectively limit access to a system resource controllable by the instructions when executed by the CPU during a pre-boot runtime of the processing systems,

wherein the firmware instructions selectively limit access to the system resource by determining a class of a requester for the system resource and associating the class with a class allocation amount for the system resource,

wherein selectively limiting access to the system resource includes granting access to the system resource if the first amount plus the second amount do not exceed the class allocation amount.

18. The processing system of claim 17, wherein the instructions include a resource configuration (“

RC”

) matrix to correlate the class allocation amount of the class with the system resource.

19. The processing system of claim 17, further comprising a resource configuration (“

RC”

) matrix to correlate the class allocation amount of the class with the system resource, the RC matrix stored on another memory device communicatively coupled to the CPU.

20. The processing system of claim 17 wherein the instructions selectively limit access to the system resource by denying access to the system resource when a request to use the system resource by the requester would exceed the class allocation amount for the class of the requester.

21. The processing system of claim 17 wherein the class allocation amount comprises a ratio of the system resource.

22. The processing system of claim 17 wherein the class allocation amount comprises a fixed amount of the system resource.

23. The processing system of claim 17 wherein the requester comprises an attached device communicatively coupled to the CPU and the system resource via a data bus to send and to receive data over the data bus and to use the system resource.

24. The processing system of claim 23 wherein the attached device comprises an add-in device.

25. The processing system of claim 17 wherein the requester comprises a operating system software running on the processing system.

26. The processing system of claim 17 wherein the system resource comprises non-volatile memory.

27. The processing system of claim 17 wherein the system resource comprises system random access memory.

28. The processing system of claim 17, wherein the instructions are also executable by the CPU during an operating system (“

OS”

) runtime of the processing system to selectively limit access to the system resource during the OS runtime.