Patent Application
20130074085
Portable computing devices (PCDs) are ubiquitous. These devices may include cellular telephones, portable digital assistants (PDAs), portable game consoles, palmtop computers, and other portable electronic devices. In addition to the primary function of these devices, many include peripheral functions. For example, a cellular telephone may include the primary function of making cellular telephone calls and the peripheral functions of a still camera, a video camera, global positioning system (GPS) navigation, web browsing, sending and receiving emails, sending and receiving text messages, push-to-talk capabilities, etc. As the functionality of such a device increases, the computing or processing power required to support such functionality also increases. Further, as the computing power increases, there exists a greater need to effectively manage the processor, or processors, that provide the computing power.
Accordingly, what is needed is an improved method of controlling power within a multicore CPU.
The accompanying drawings, which are incorporated herein and constitute part of this specification, illustrate exemplary aspects of the invention, and together with the general description given above and the detailed description given below, serve to explain the features of the invention.
The various aspects will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.
In this description, the term “application” may also include files having executable content, such as: object code, scripts, byte code, markup language files, and patches. In addition, an “application” referred to herein, may also include files that are not executable in nature, such as documents that may need to be opened or other data files that need to be accessed.
The term “content” may also include files having executable content, such as: object code, scripts, byte code, markup language files, and patches. In addition, “content” referred to herein, may also include files that are not executable in nature, such as documents that may need to be opened or other data files that need to be accessed.
As used in this description, the terms “component,” “database,” “module,” “system,” and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be a component. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components may execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
Referring initially to
In a particular aspect, as depicted in
Referring to
As illustrated in
As further illustrated in
As depicted in
In a particular aspect, one or more of the method steps described herein may be stored in the memory 344 as computer program instructions. These instructions may be executed by the multicore CPU 324 in order to perform the methods described herein. Further, the multicore CPU 324, the memory 344, or a combination thereof may serve as a means for executing one or more of the method steps described herein in order to a dynamically control the power of each CPU, or core, within the multicore CPU 324.
Referring to
Moreover, as illustrated, the memory 404 may include an operating system 420 stored thereon. The operating system 420 may include a scheduler 422 and the scheduler 422 may include a first run queue 424, a second run queue 426, and an Nth run queue 428. The memory 404 may also include a first application 430, a second application 432, and an Nth application 434 stored thereon.
In a particular aspect, the applications 430, 432, 434 may send one or more tasks 436 to the operating system 420 to be processed at the cores 410, 412, 414 within the multicore CPU 402. The tasks 436 may be processed, or executed, as single tasks, threads, or a combination thereof. Further, the scheduler 422 may schedule the tasks, threads, or a combination thereof for execution within the multicore CPU 402. Additionally, the scheduler 422 may place the tasks, threads, or a combination thereof in the run queues 424, 426, 428. The cores 410, 412, 414 may retrieve the tasks, threads, or a combination thereof from the run queues 424, 426, 428 as instructed, e.g., by the operating system 420 for processing, or execution, of those task and threads at the cores 410, 412, 414.
Referring to
At block 504, a power controller, e.g., a dynamic clock and voltage scaling (DCVS) algorithm, may monitor one or more CPUs. At decision 506, the power controller may determine whether a transient performance deadline for a CPU has expired. If not, the method 500 may end. Otherwise, if the transient performance deadline has expired, the method 500 may proceed to block 508 and the power controller may move the CPU to a higher performance level, i.e., a next higher operating frequency. In one aspect, the controller may move the CPU to a maximum performance level, i.e., a maximum CPU frequency. However, in another aspect, the CPU may not jump to a maximum performance level. The CPU may jump to an intermediate level and then, jump again, either to the maximum level or another higher performance level. The number of intermediate jumps, and the amount of time between jumps, may be used to determine the frequency value of the jump.
At block 510, the CPU may enter an idle condition. Further, at block 512, the transient performance deadline may be reset. At block 514, the CPU may exit the idle condition. Moving to decision 516, the power controller may determine whether the upcoming CPU frequency is at a maximum CPU frequency. If so, the method 500 may end. Otherwise, if the CPU frequency is not at the maximum CPU frequency, the method may proceed to block 518 and the timer may be rescheduled. Then, the method 500 may end.
Referring to
At block 608, the CPU may enter a software wait for interrupt (SWFI) condition. At block 610, the CPU may exit the SWFI condition. Moving to block 612, the power controller may set an end idle time (EndIdleTime) equal to a current time (CurrentTime). Further, at block 614, the power controller may determine an idle time (IdleTime) by subtracting the start idle time (StartIdleTime) from the end idle time (EndIdleTime). At block 616, the power controller may determine an upcoming CPU frequency (CPUFreq) from an updated steady state filter (UpdateSteadyStateFilter) a busy time (BusyTime) and an idle time (IdleTime). Thereafter, the method 600 may continue to block 702 of
At block 702, the power controller may determine an effective transient budget (EffectiveTransientBudget) using the following formula:
EffectiveTransientBudget=(TransientResponseDeadline*NextCPUFreq)/(Next CPUF−req-CPUFreq)
where,
TransientResponseDeadline=A transient response deadline, i.e., slack budget,
NextCPUFreq=A next CPU frequency that is one frequency step higher than an upcoming CPU frequency, and
CPUFreq=An upcoming CPU frequency (CPUFreq).
In a particular aspect, a clock scheduling overhead (ClockSchedulingOverhead) and a clock switch overhead (ClockSwitchOverhead) may also be added to the EffectiveTransientBudget. Further, a voltage change overhead (VoltageChangeOverhead) may be added to the EffectiveTransientBudget. Moving to block 704, the power controller may set a deadline to jump to a higher frequency (SetJumpToFrequency) equal to the end idle time (EndIdleTime) plus the effective transient budget (EffectiveTransientBudget). In another aspect, the deadline to jump may be the current time plus the transient budget. Thereafter, the method 600 may end.
In a particular aspect, the method 600 described in conjunction with
It is to be understood that the method steps described herein need not necessarily be performed in the order as described. Further, words such as “thereafter,” “then,” “next,” etc. are not intended to limit the order of the steps. These words are simply used to guide the reader through the description of the method steps. Moreover, the methods described herein are described as executable on a portable computing device (PCD). The PCD may be a mobile telephone device, a portable digital assistant device, a smartbook computing device, a netbook computing device, a laptop computing device, a desktop computing device, or a combination thereof.
In a particular aspect, a DCVS algorithm is a mechanism which measures CPU load/idle time and dynamically adjusts the CPU clock frequency to track the workload in an effort to reduce power consumption while still providing satisfactory system performance. As the workload changes, the change in CPU throughput may track, but also necessarily lag, the changes in the workload. Unfortunately, this may introduce a problem in cases where the workload has Quality of Service (QoS) requirements, as the DCVS algorithm may not track the workload quickly enough. Further, tasks may fail.
Many DCVS techniques involve measuring the steady state performance requirements of the CPU and setting the CPU frequency and voltage to the lowest level that may meet the steady state CPU usage. This is typically done by measuring the CPU utilization (percentage busy) over a period of time and setting the CPU performance level to one in which the average CPU utilization falls between a high and low threshold. The averaging period is optimized to minimize the frequency of changing clock frequencies, while maintaining reasonable responsiveness. In order to respond to transient workloads and/or the start of new workloads panic inputs may have been utilized to quickly bring up the CPU frequency.
In order to avoid the problem of the DCVS lagging the workload and causing tasks to fail, the system and methods disclosed herein provide a transient performance guarantee. The transient performance guarantee may be defined as the maximum amount of time that a continuously busy pulse may be delayed, as compared to running at the higher performance level. This may be accomplished by getting to the higher performance level prior to the transient performance deadline expiring and resetting the deadline whenever we go idle, since if the CPU is idle, it is by definition not in an oversubscribed state. As disclosed herein, the timer may be rescheduled to preserve the QoS guarantee whenever the system comes out of idle and the system CPU is not running at the maximum frequency.
In order to minimize the power impact of the transient performance guarantee, the present system and methods minimize the likely hood that an incoming pulse may require a frequency increase in order to meet the deadline. This may be accomplished by delaying the frequency, i.e., performance level, change until the effective transient budget has been exhausted and then, jumping straight to the higher performance level and staying there until the pulse is complete as shown in
In a particular aspect, the effective transient budget is calculated as the transient response deadline scaled to the current performance level. For example, if the CPU is running a 75% of the maximum clock rate and the transient response deadline is 16 ms, the effective transient budget is 64 ms, i.e., 16 ms/(1−0.75). The effective transient budget represents how long the CPU may run at the current performance level prior to exhausting the budget. If the CPU is idle, the effective transient budget may be the same as the transient response deadline. If we are at the maximum performance level, the effective transient budget is infinite as shown in
Using the methods described herein, the system may provide a strict bound on the maximum amount of time a task might run at some level other than the maximum level, and therefore implicitly provide a calculable bound on completion for tasks that require QoS guarantees, while still allowing dynamic CPU clock scaling. The bound may be set based on what tasks are currently running, a global system property, DCVS algorithm design or other properties, and may be entirely disabled if the system is not running any tasks that have QoS requirements or if the CPU is running at max clock.
In a particular aspect, the present methods may be extended by, instead of jumping to the maximum frequency when the deadline has expired, setting shorter internal effective deadlines and jumping to one, or more, intermediate frequencies, while still ensuring that the CPU is at the maximum frequency before the maximum QoS delay has been exhausted. Further, the present methods may substantially ensure that a well defined transient QoS is maintained, while simultaneously reducing overall CPU power.
The system and methods described herein may utilize opportunistic sampling. In other words, the system and methods may check for timer expiration on a periodic basis. In other aspects, the system and methods may not utilize opportunistic sampling.
As discussed above, the various aspects provide a strict and calculable bound (e.g., a performance guarantee) for the completion for tasks. In various aspects, such performance guarantees may be implemented as part of a dynamic clock and voltage/frequency scaling (DCVS) solution to improve processor performance and/or reduce power consumption on portable computing devices (PCDs), including mobile devices such as cellular telephones, smartphones, personal or mobile multi-media players, personal data assistants (PDA's), laptop computers, tablet computers, smartbooks, ultrabooks, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, and similar personal electronic devices that include a memory, a programmable processor or core (herein collectively “processing core”) and operate under battery power such that power conservation methods are of benefit. Further, while the various aspects are particularly useful for portable and mobile computing devices that run on battery power, the aspects are generally useful in any computing device (e.g., general-purpose computers, desktop computers, servers, etc.) that includes a processor and for which reduced power consumption is beneficial.
Generally, the dynamic power (switching power) dissipated by a chip is C*V2*f, where C is the capacitance being switched per clock cycle, V is voltage, and f is the switching frequency. Thus, as frequency changes, the dynamic power will change linearly with it. Dynamic power may account for approximately two-thirds of the total power consumed by a processor chip. Voltage scaling may be accomplished in conjunction with frequency scaling, because the frequency at which a chip runs may be related to its operating voltage. The efficiency of some electrical components, such as voltage regulators, may decrease with increasing temperature so that the power consumption increases with temperature. Since increasing power use may increase the temperature, increases in voltage or frequency may increase system power demands even further. Thus, the battery life of a computing device may be improved by reducing the frequency and/or voltage applied to its processors when they are idle or lightly loaded. Such reductions in frequency and/or voltage may be accomplished in real time or “on the fly” via a dynamic clock and voltage/frequency scaling (DCVS) solution.
Generally, a DCVS solution monitors the proportion of the time that a processor is idle (compared to the time it is busy), and determines how much the frequency/voltage of the processors should be adjusted based on the proportion of the time the processors is idle and/or busy. Monitoring the proportion of the time that a processor is idle may include computing and/or measuring a value (e.g., amount of time, number of CPU cycles, etc.) indicative of the duration that the processor executes an idle process or thread (e.g., a system idle process, etc.).
An operating system may execute an idle software application, process, or thread (herein collectively “thread”) on the processor when it determines that there are no other threads ready to be scheduled on that processor. The idle thread may perform various tasks (e.g., wait for interrupt task, sleep task, etc.), and each task may include a number of processor operations. When a processor executes an idle thread, that processor may be said to be “idle” in an “idle state,” and/or in an “idle condition.”
In multiprocessor systems, an operating system (or scheduler, controller, etc.) may maintain one or more idle threads for each processor. Idle threads remain ready for execution so that each processor always has a thread ready to execute. In this manner, whenever a thread relinquishes a processor (e.g., due to the thread completing its scheduled tasks or workloads), the operating system has a thread ready for execution on that processor (e.g., via the availability of the idle thread), even when all other threads are complete, waiting for resources, or otherwise not currently ready to execute.
As discussed above, a DCVS solution may adjust a processor's frequency and/or voltage based on that processor's workloads, which may include a steady state workload. A steady state workload may be determined in advance of execution time, that is in advance of the processing core entering a busy or active state to perform operations in furtherance of the workload. The steady state workload may be determined in advance by computing, estimating, or predicting the number of CPU clock cycles, number of operations, number of instructions, and/or amount of time required to complete the tasks scheduled on that processing core. Each processor may have more than one workload (e.g., a steady state workload and a transient workload), and each processor may be required to remain in a busy, running, or active state (herein collectively “busy state”) until all the tasks in all its workloads are complete.
In certain scenarios, a DCVS solution may reduce a processor's frequency and/or voltage (i.e., the processor's speed) to achieve power savings without impacting the processor's performance. For example, when the processor's workload includes a task whose execution time is dominated by memory access times, a reduction in frequency may not have a significant impact on that processor's performance or that task's execution time. However, more often, the DCVS solution must balance tradeoffs between the processor's performance (e.g., time required to complete a given set of tasks, etc.) and power consumption (e.g., amount of battery power consumed in accomplishing the given set of tasks) characteristics. Typically, the faster the tasks are accomplished, the more power is consumed by the processor in accomplishing those tasks.
A DCVS solution may be configured to balance the performance and power consumption based on a processor's steady state workload and steady state performance requirements. The steady state performance requirements may be determined by computing or measuring a value (e.g., amount of time, number of CPU cycles, etc.) indicative of a duration in which the processor is busy and/or idle, averaging the results of the computed/measured values, and determining the amount of time/processing that is required to complete that processor's steady state workloads. Based on these computations, the DCVS solution may compute an upper frequency threshold and a lower frequency threshold within which the processor may operate to meet the computed steady state requirements while achieving reduced power consumption and acceptable levels of responsiveness (e.g., such that a mobile device user does not notice a difference, etc.).
Often, processors are required to process/execute transient workloads, which include “bursts of work” that the DCVS solution was not informed of a priori, and which were not accounted for in the steady state or frequency threshold computations. A transient workload may be any task or unit of work that is not known to the system in advance, including any unit of work that is dynamic, temporary, or which causes an unexpected spike in the processor's workload. By way of example, a transient workload may include any or all of tasks performed by a processor in response to user inputs, system events, detected environmental conditions, remote procedure calls, etc. As a further example, a transient workload may be generated when a user touches a touch-screen of a portable computing device (PCD) to initiate a user action, to which the PCD must respond immediately (e.g., with an interface update, by displaying a new image, launching a new action, etc.).
As mentioned above, transient workloads are not continuous steady state workloads for which the DCVS solution can properly account for in advance (e.g., as part of determining the upper and lower thresholds). As a result, a transient workload may cause a processor to remain in a busy state for longer than expected and/or otherwise result in uncertainties in processor execution times. Such uncertainties may cause the computing device to allocate processing and system resources inefficiently or improperly, and may have a significant impact on the overall performance and/or responsiveness of a computing device, especially when the computing device includes multiple processing cores.
Modern computing devices are often multiprocessor systems that include system-on-chips (SoCs) and/or multiple processing cores (e.g., processors, cores, etc.). In multiprocessor systems, it is common for a single thread to be processed by a first processing core, then by a second processing core, and then again by the first processing core. It is also common for the results of one thread in a first processing core to trigger operations in another thread executing in a second processing core. For example, one or more processing cores may be dependent on the results generated by a currently active processor, and may be required to remain in an idle or wait state until the currently active processor completes its workloads and/or finishes processing one or more tasks. In these situations, each processing core may alternatively enter an idle/wait state while it awaits the results of processing from the currently active processor. While these processing cores wait for the results generated by the currently active processor, their respective DCVS solutions may reduce their operating speeds (i.e., via a reduction in frequency/voltage), causing the computing device to appear non-responsive or slow. That is, a DCVS solution implemented on multiprocessor computing devices may incorrectly conclude that the some of the processing cores should be operated at lower frequency or voltage than is optimal for running the currently active threads, and cause the computing device to appear non-responsive or slow.
The various aspects overcome the above mentioned limitations by computing and enforcing performance guarantees that ensure a processing core does not remain in a busy state (e.g., due to transient workloads) for more than a predetermined amount of time above which is required for that processing core to complete its pre-computed steady state workload. Such performance guarantees may be used by the operating system, resources, DCVS solutions, and/or other processing cores to better estimate, schedule, and/or plan future operations, such as allocating resources and scheduling threads for execution. In this manner, the performance guarantees enable the computing device to meet its responsiveness requirements, and thus improve the user experience.
Performance guarantees allow a DCVS solution to adjust the frequency and/or voltage of a processor based on a variable delay, which ensures that the processing core only falls behind its steady state workload by, at most, a defined maximum amount of work, irrespective of the current or previous operating frequencies/voltages of the processor.
The hardware unit 1002 may include a number of processing cores (e.g., CPU 0, CPU 1, 2D-GPU 0, 2D-GPU 1, 3D-GPU 0, etc.) and a resources module 1020 that includes various hardware resources (e.g., clocks, power management integrated circuits or “PMICs,” scratchpad memories or “SPMs,” etc.) shared by the processing cores.
The kernel space software unit 1004 may include processor modules (CPU_0 Idle stats, CPU_1 idle stats, 2D-GPU_0 driver, 2D-GPU_1 driver, 3D-GPU_0 driver, etc.) that correspond to at least one of the processing cores in the hardware unit 1002, each of which may communicate with one or more idle stats device modules 1008. The kernel space software unit 1004 may further include a timer driver module 1014, input event modules 1010, and a CPU request stats module 1012. In an aspect, the timer driver module 1014 may drive (or maintain) a timer for each processing core.
The user space software unit 1006 may include a DCVS control module 416 configured to receive inputs from each of the idle stats device modules 1008, input event modules 1010, timer driver module 1014, and CPU request stats module 1012, and/or to send outputs to a CPU frequency hot-plug module 1018. The CPU frequency hot-plug module 1018 may be configured to send communication signals to the resources module 1020. The CPU frequency hot-plug module 1018 may be further configured to apply voltage/frequency changes to each core, either individually (e.g., one at a time, sequentially, etc.) or simultaneously (e.g., at approximately the same point in time).
The DCVS control module 1016 may include threads suitable for execution on any or all of the processing cores (e.g., CPU 0, CPU 1, 2D-GPU 0, 2D-GPU 1, 3D-GPU 0, etc.) and/or suitable for implementing a DCVS solution on the computing device 1000. In an aspect, the DCVS control module 1016 may include a thread that monitors a port or a socket for an occurrence of an event (e.g., filling of a data buffer, expiration of a timer, state transition, etc.) that causes the DCVS control module 1016 to collect information from one or more processing cores and perform DCVS operations on a processing core. In an aspect, the DCVS control module 1016 may include a single-threaded DCVS solution that monitors two or more processing cores. In an aspect, the DCVS control module 1016 may include a DCVS solution thread for each processing core.
In an aspect, the DCVS control module 1016 may be configured to generate pulse trains. The DCVS control module 1016 may generate the pulse trains by monitoring or sampling the busy and/or idle states (or the transitions between states) of the processing cores. The DCVS control module 1016 may also generate the pulse trains based on information obtained from monitoring the depth of one or more processor run-queues. A run-queue may include a running thread as well as a collection of one or more threads that are capable of running on a processing core, but not yet able to do so (e.g., due to another active thread that is currently running, etc.). Each processing core may have its own run-queue, or a single run-queue may be shared my multiple processing cores. Threads may be removed from the run queue when they request to enter a sleep state, are waiting on a resource to become available, or have been terminated. Thus the number of threads in the run queue (i.e., the run queue depth) may identify the number of active threads (e.g., waiting, running), including the thread currently being processed (running) and the thread waiting to be processed.
In an aspect, the DCVS control module 1016 may be configured to compute steady state workloads, steady state requirements, and/or upper and lower frequency/voltage thresholds based on the generated pulse trains. The upper and lower frequency/voltage thresholds may define a frequency/voltage rage within which a processing core may operate to meet the its steady state performance requirements while simultaneously achieving reduced power consumption and meeting the responsiveness requirements of the computing device 1000. Meeting the responsiveness requirements may include performing all the tasks in the workloads so that a user of the computing device 1000 does not notice a reduction in the computing device's performance or speed.
The DCVS control module 1016 may be configured to monitor the overall computing device 1000 performance and/or insure that one or more of the processing cores operate between established upper and lower frequency thresholds. The DCVS control module 1016 may adjust processing resources and/or the operating frequencies of the processing cores so that they are commensurate with the thresholds.
As discussed above, the DCVS control module 1016 may generate pulse trains. In an aspect, pulse trains generated for two or more of the processing cores may be synchronized in time and cross-correlated to generate correlation models that include information suitable for determining whether the processing cores are performing operations that are co-operative and/or dependent on one another. In an aspect, the DCVS control module 1016 may use the correlation models to determine the upper and lower frequency thresholds, initial operating frequency, steady state requirements, and processor workloads so that these value account for the interdependencies between the processing cores.
In an aspect, the DCVS control module 1016 may be configured to compute and/or enforce performance guarantees. As mentioned above, processing cores may be required to process/execute transient workloads that the DCVS solution cannot properly account for in advance. Thus, transient workloads may cause the DCVS control module 1016 to operate one or more of the processing cores at a sub-optimal frequency level or within a sub-optimal frequency range. For example, since the DCVS control module 1016 cannot account for the transient workloads in advance, it may improperly conclude that the processing core may be operated at a lower frequency level than that which is required to complete both the steady state workload and the transient workload in a time period that suitable for meeting the responsiveness requirements of the computing device 1000.
A performance guarantee provides the computing device 1000 with a strict and calculable bound that may be used by the DCVS control module 1016 to ensure a processing core does not remain in a busy state (e.g., due to transient workloads) for more than a predetermined amount of time/work above that which is required for that processing core to complete its steady state workload requirements. A performance guarantee allows the DCVS control module 1016 to ensure that a processing core completes both its steady state workload and its transient workloads in a time period that suitable for meeting the responsiveness requirements of the computing device 1000.
In various aspects, a performance guarantee may be computed in, defined in, and/or include any unit of measurement suitable for measuring processor performance or a duration, such as an amount of time, an amount of work, a number of tasks, a number of instructions, a number of CPU cycles, etc. In various aspects, a performance guarantee may be associated with a frequency and/or may be a function of frequency.
In an aspect, a performance guarantee may include one or more performance guarantee values. In the various aspects, the performance guarantee values (e.g., a deadline value, a budget value, a jump-to-max value, etc.) may be expressed in any unit of measurement suitable for measuring processor performance or a duration, such as an amount of time, an amount of work, a number of tasks, a number of instructions, a number of CPU cycles, etc.
In various aspects, the performance guarantee values may include a budget value (e.g., slack budget, transient budget, etc.), a deadline value (e.g., transient deadline, transient response deadline, performance deadline, etc.), and/or a jump-to-max value.
The deadline value may be a value indicative of a relative time before which the processing core is to complete its workload processing and/or a value indicative of a relative time after which the frequency of a processing core is to be increased.
The budget value may be a value indicative of an amount of time remaining before which the processing core is to complete its workload processing and/or after which the frequency of a processing core is to be increased.
The jump-to-max value may be a value indicative of a relative time before which the processing core is to complete its workload processing and/or after which the frequency of a processing core is to be increased to the maximum frequency.
The performance guarantee values may be a related to, associated with, and/or function of frequency or voltage. For example, each of the budget, deadline, and/or jump-to values may be a time value that is computed as a function of an operating frequency of a corresponding processing core. Thus, each of these values may be 10 milliseconds when the processing core operates at a frequency of 100 MHz, 20 milliseconds at a frequency of 200 MHz, 40 milliseconds at a frequency of 400 MHz, etc. In the manner, the performance guarantee values may used by the DCVS solution to implement a variable delay for increasing the frequency of a processing core.
As mentioned above and illustrated in
In an aspect, the DCVS control module 1016 may be configured to set the deadline value to be equal to the budget value each time the corresponding processing core transitions from idle to busy, enters a busy state (e.g., beings processing the workload, etc.) and/or exits the idle state (e.g., when an idle thread relinquishes the processing core, etc.).
In an aspect, the DCVS control module 1016 may be configured to set or reset an existing deadline value each time the corresponding processing core transitions from busy to idle, enters an idle state (e.g., beings executing an idle thread, etc.) and/or exits the busy state (e.g., completes all tasks in the workload, etc.).
In block 1102, a DCVS solution may cause a processing core to transition from an idle state to a busy state. In block 1104, the DCVS solution may set the value of an end idle time parameter (EndIdleTime) to be equal to a current time value (CurrentTime). Thus, the end idle time parameter (EndIdleTime) may store a value that is indicative of the time at which the processing core last exited the idle state.
In various aspects, the operations of blocks 1102 and 1104 may be performed sequentially, in parallel, and/or in any order. For example, in an aspect, the DCVS solution may set the value of an end idle time parameter (EndIdleTime) before transitioning the processing core from idle to busy. In another aspect, the DCVS solution may set the value of an end idle time parameter (EndIdleTime) after transitioning the processing core from idle to busy.
In block 1106, the DCVS solution may monitor the operating frequency or voltage of the processing core and make adjustments as necessary. In block 1108, the DCVS solution may cause the processing core to transition from the busy state to the idle state. In an aspect, the DCVS solution may transition the processing core to the idle state by commencing execution of an idle thread on the processing core. In an aspect, the DCVS solution may transition the processing core to the idle state after the processing core completes all the tasks associated with all its workloads.
In optional block 1110, the DCVS solution may set or reset an existing deadline value. As discussed above, a deadline value may be a performance guarantee value that is included in, or associated with, a performance guarantee. Additional details regarding the operations of setting, reset, and/or computing the deadline value are provided further below.
In block 1112, the DCVS solution may set the value of a start idle time parameter (StartIdleTime) to be equal to a current time value (CurrentTime). In block 1114, the DCVS solution may set the value of a busy time parameter (BusyTime) to be equal to the difference between the time when the processing core last exited a previous idle state (which may be represented by the end idle time parameter “EndIdleTime”) and the time when the processing core entered the current idle state (which may be represented by the start idle time parameter “StartIdleTime”). Thus, the busy time parameter (BusyTime) may store a value that is indicative of a duration in which the processing core most recently remained in the busy state.
In block 1116, the DCVS solution may cause the processing core to perform various idle state operations, such as sleep operations, deep sleep operations, or software wait for interrupt operations. Accordingly, in block 1116, the DCVS solution (e.g., via the idle thread, operating system, etc.) may cause the processing core to enter a sleep state, a deep sleep state, a wait for interrupt state, etc.
In block 1118, the DCVS solution and/or idle thread may receive an interrupt request and/or otherwise determine that the processing core is to be transitioned from its current state to a busy state. This may be achieved by DCVS solution receiving a notification (e.g., from an operating system scheduler, controller, etc.) that tasks have been scheduled for execution on the processing core and/or scheduled tasks are ready for execution.
In block 1120, the DCVS solution may set the value of the end idle time parameter (EndIdleTime) to be equal to a current time value (CurrentTime). In block 1122, the DCVS solution may set the value of an idle time parameter (IdleTime) to be equal to a difference between the value of the StartldleTime parameter and the value of the EndIdleTime parameter. Thus, the idle time parameter (IdleTime) may store a value indicative of the duration in which the processing core last remained the idle state.
In block 1124, the DCVS solution may compute an operating frequency, frequency range, and/or frequency thresholds within which the processing core is to operate. In an aspect, the DCVS solution may compute the frequency or frequency range based on the duration of time the processing core last remained in a busy state (e.g., BusyTime) and/or the duration of time the processing core last remained in the idle state (e.g., IdleTime). In an aspect, the DCVS solution may compute the operating frequency, frequency range, and/or frequency thresholds based on historical information, such as an average (or moving average) of the durations in which the processor previously remained in the busy and/or idle states (e.g., over a predetermined time period or time window). In an aspect, the DCVS solution may compute the operating frequency, frequency range, and/or frequency thresholds based on pulse trains. As discussed above, pulse trains may be generated based on a sampling of the busy and/or idle states, transitions between states, depth of run-queues, etc.
In block 1126, the DCVS solution may compute or select a deadline value. The deadline value may be a value that is indicative of a relative time after which the frequency of the processing core is to be set to be increased, either to a next higher frequency step or to the maximum frequency. In various aspects, the deadline value may computed based on configuration settings, driver inputs, the quantity and/or types of scheduled tasks, the predicted steady state workload, and/or the responsiveness requirements of the computing device. The deadline value may be determined based on static and/or dynamic values. For example, the deadline value may be determined based on a static configuration value, or based on the types of tasks (e.g., streaming 1080p video vs. streaming 720p video, etc.) scheduled to be performed on the processing core.
In an aspect, the deadline value may be inversely proportional to the responsiveness requirements of the computing device (i.e., the higher the responsiveness requirements, the shorter the deadline). In an aspect, the deadline value may be a time value that is a function of a current operating frequency of the processing core (e.g., 10 milliseconds at a frequency of 100 MHz, 20 milliseconds at a frequency of 200 MHz, 40 milliseconds at a frequency of 400 MHz, etc.).
In block 1128, the DCVS solution may compute or select a budget value. The budget value may be a value that is indicative of an amount of time in which the processing core may remain in the active or busy state without exceeding the sum of the deadline value and the time determined to be required for the processing core to complete its steady state workload requirements. In an aspect, the budget value may be a time value that is a function of a current operating frequency of the processing core (e.g., 10 milliseconds at a frequency of 100 MHz, 20 milliseconds at a frequency of 200 MHz, 40 milliseconds at a frequency of 400 MHz, etc.).
In various aspects, the budget value may computed based on the deadline value, a plurality of frequency levels or steps, the maximum processor frequency, a steady state processor frequency, etc. In an aspect, the budget value may an effective transient budget and/or computed via any of the formulas discussed above.
In optional block 1130, the DCVS solution may compute a jump to max value. The jump-to-max value may be a value that is indicative of a relative time after which the frequency of the processing core is to be set the maximum processing frequency. In an aspect, the jump-to-max value may be computed by summing the value of the EndIdleTime parameter and the budge value.
In block 1132, the DCVS solution may transition the processing core from the idle state to a busy state. In an aspect, as part of block 1132, the DCVS solution may set the deadline value to be equal to the budget value. In various aspects, the DCVS solution may be configured to set the deadline value to be equal to the budget value each time the processing core transitions from idle to busy, enters an active or busy state (e.g., beings processing the workload, etc.) and/or exits an idle state (e.g., when an idle thread relinquishes the processing core, etc.).
In block 1206, the DCVS solution may compute and set the initial operating frequency and/or various performance guarantee values (e.g., deadline value, budget value, jump-to-max value, etc.). In block 1208, the DCVS solution may compute the amount of time or work (e.g., CPU cycles, instructions, etc.) required for the processing core to complete all the tasks in the steady state workload while meeting the various performance requirements.
In block 1210, the DCVS solution may transition the processing core from an idle state to a busy state so that the processing core runs at the computed initial operating frequency/voltage (or within the computed thresholds) and/or meets the various device or system requirements. In block 1212, the DCVS solution may monitor the actual workload and/or operating frequency of the processing core and adjust the frequency/voltage as necessary (e.g., in accordance with a default clock and voltage scaling algorithm). In optional block 1214, the DCVS solution may update the performance guarantee values based on the current operating frequency/voltage of the processing core.
In determination block 1216, the DCVS solution may determine whether the processing core has remained in the busy state longer than the computed time/work (i.e., the amount of time/work determined to be required for the processing core to complete all the tasks in the predicted steady state workload). When the DCVS solution determines that the processing core has not remained in the busy state for longer than the computed time/work (i.e., determination step 1216=“No”), in block 1212, the DCVS solution may continue to monitor the actual workload/frequency and make adjustments when necessary.
When the DCVS solution determines that the processing core has remained in the busy state for a duration that is longer than the computed time/work (i.e., determination step 1216=“Yes”), in determination block 1218, the DCVS solution may determine whether the budget has been exhausted. The DCVS solution may determine that the budget has been exhausted when the budget value equals zero and/or when the processing core has remained in the busy state for a duration (measured in either time or work) that is greater than or equal to the deadline value plus the computed time/work.
When the DCVS solution determines that the budget has not been exhausted (i.e., determination step 1218=“No”), in block 1212, the DCVS solution may continue to monitor the actual workload/frequency and make adjustments as necessary. When the DCVS solution determines that the budget has been exhausted (i.e., determination step 1218=“Yes”), in block 1220, the DCVS solution may increase the operating frequency/voltage of the processing core. In an aspect, the DCVS solution may increase operating frequency/voltage of the processing core to the maximum processor frequency in block 1220. In an aspect, the DCVS solution may increase operating frequency/voltage thresholds in block 1220. In an aspect, in block 1220, the DCVS solution may increase operating frequency/voltage of the processing core in steps.
When the DCVS solution determines that the there is a high probably that the processing core will complete its current workload before the computed time plus the deadline value (i.e., determination step 1316=“Yes”), in block 1312, the DCVS solution may continue to monitor the actual workload/frequency and make adjustments to the operating frequency/voltage as necessary.
When the DCVS solution determines that the there is not a high probably that the processing core will complete its current workload before the computed time value plus the deadline value (i.e., determination step 1316=“No”), in block 1318, the DCVS solution may increase the operating frequency/voltage of the processing core. The operating frequency/voltage of the processing core may be increased to the maximum processor frequency or in steps.
Various aspects include methods of improving performance on a computing device having a processor, which may include determining a steady state workload of the processor, determining an amount of work required to perform the determined steady state workload on the processor, computing a performance guarantee value for the processor, transitioning the processor from an idle state to a busy state, performing dynamic clock and voltage scaling operations to scale a frequency of the processor based on an actual workload of the processor, updating the performance guarantee value based on the scaled frequency, determining whether the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In an aspect, increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the processor to a maximum processor frequency. In a further aspect, increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the processor in steps. In a further aspect, the method may further include repeatedly performing the operations of updating the performance guarantee value based on the scaled frequency, determining whether the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In a further aspect, computing a performance guarantee value for the processor may include computing a deadline value. In a further aspect, computing a performance guarantee value for the processor may include computing a budget value. In a further aspect, determining a steady state workload of the processor may include determining requirements of tasks scheduled to execute on the processor. In a further aspect, the method may include generating pulse trains by sampling transitions between the busy and idle states. In a further aspect, the operations of determining a steady state workload of the processor, determining an amount of work required to perform steady state workload on the processor, and computing a performance guarantee value for the processor are performed by a single thread. In a further aspect, the single thread executes on the processor. In a further aspect, the single thread executes on a second processor of the computing device.
Further aspects include a computing device having means for determining a steady state workload of the processor, means for determining an amount of work required to perform the determined steady state workload on the processor, means for computing a performance guarantee value for the processor, means for transitioning the processor from an idle state to a busy state, means for performing dynamic clock and voltage scaling operations to scale a frequency of the processor based on an actual workload of the processor, means for updating the performance guarantee value based on the scaled frequency, means for determining whether the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and means for increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In an aspect, means for increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include means for increasing the frequency of the processor to a maximum processor frequency.
In a further aspect, means for increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include means for increasing the frequency of the processor in steps. In a further aspect, the computing device may further include means for repeatedly performing the operations of updating the performance guarantee value based on the scaled frequency, determining whether the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the processor when it is determined that the processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In a further aspect, means for computing a performance guarantee value for the processor may include means for computing a deadline value. In a further aspect, means for computing a performance guarantee value for the processor may include means for computing a budget value. In a further aspect, means for determining a steady state workload of the processor may include means for determining requirements of tasks scheduled to execute on the processor. In a further aspect, the computing device may include means for generating pulse trains by sampling transitions between the busy and idle states.
In a further aspect, the computing device may include means for accomplishing the operations of determining a steady state workload of the processor, determining an amount of work required to perform steady state workload on the processor, and computing a performance guarantee value for the processor via a single thread. In a further aspect, the computing device may include means for executing the single thread on the processor. In a further aspect, the computing device may include means for executing the single thread on a second processor of the computing device.
Further aspects include a computing device that may include a processor configured with processor-executable instructions to perform operations that may include a first processor configured with processor-executable instructions to perform operations including determining a steady state workload of a second processor, determining an amount of work required to perform the determined steady state workload on the second processor, computing a performance guarantee value for the second processor, transitioning the second processor from an idle state to a busy state, performing dynamic clock and voltage scaling operations to scale a frequency of the second processor based on an actual workload of the second processor, updating the performance guarantee value based on the scaled frequency, determining whether the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In an aspect, the first processor may be configured with processor-executable instructions such that increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the second processor to a maximum processor frequency.
In a further aspect, the first processor may be configured with processor-executable instructions such that increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the second processor in steps.
In a further aspect, the first processor may be further configured with processor-executable instructions to repeatedly perform the operations of updating the performance guarantee value based on the scaled frequency, determining whether the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value. In a further aspect, the first processor may be configured with processor-executable instructions such that computing a performance guarantee value for the second processor may include computing a deadline value.
In a further aspect, the first processor may be configured with processor-executable instructions such that computing a performance guarantee value for the second processor may include computing a budget value. In a further aspect, the first processor may be configured with processor-executable instructions such that determining a steady state workload of the second processor may include determining requirements of tasks scheduled to execute on the second processor. In a further aspect, the first processor may be configured with processor-executable instructions to perform operations further including generating pulse trains by sampling transitions between the busy and idle states.
In a further aspect, the first processor may be configured with processor-executable instructions such that the operations of determining a steady state workload of the second processor, determining an amount of work required to perform steady state workload on the second processor, and computing a performance guarantee value for the second processor are performed by a single thread. In a further aspect, the first processor may be configured with processor-executable instructions such that the single thread may be executed on the first processor. In a further aspect, the first processor may be configured with processor-executable instructions such that accomplishing the operations of determining a steady state workload of the second processor, determining an amount of work required to perform steady state workload on the second processor, and computing a performance guarantee value for the second processor may include executing the single tread on the second processor.
Further aspects include a non-transitory server-readable storage medium having stored thereon processor-executable instructions configured cause a computing device to perform operations that may include determining a steady state workload of a second processor, determining an amount of work required to perform the determined steady state workload on the second processor, computing a performance guarantee value for the second processor, transitioning the second processor from an idle state to a busy state, performing dynamic clock and voltage scaling operations to scale a frequency of the second processor based on an actual workload of the second processor, updating the performance guarantee value based on the scaled frequency, determining whether the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In an aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the second processor to a maximum processor frequency.
In a further aspect, the stored processor-executable software instructions may be configured to cause a second processor to perform operations such that increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value may include increasing the frequency of the second processor in steps, and repeatedly performing the operations of updating the performance guarantee value based on the scaled frequency, determining whether the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value, and increasing the frequency of the second processor when it is determined that the second processor has remained in the busy state for a period greater than or equal to a sum of the determined amount of work and the performance guarantee value.
In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that computing a performance guarantee value for the second processor may include computing a deadline value. In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that computing a performance guarantee value for the second processor may include computing a budget value. In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that determining a steady state workload of the second processor may include determining requirements of tasks scheduled to execute on the second processor. In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations including generating pulse trains by sampling transitions between the busy and idle states.
In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that the operations of determining a steady state workload of the second processor, determining an amount of work required to perform steady state workload on the second processor, and computing a performance guarantee value for the second processor are performed by a single thread. In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that the single thread executes on the processor. In a further aspect, the stored processor-executable software instructions may be configured to cause a processor to perform operations such that the single thread executes on the second processor.
The various aspects provide a number of benefits, and may be implemented in laptops and other mobile devices in which performance, power consumption, and/or responsiveness are important. The various aspects may be implemented in server and personal computers to decrease energy and cooling costs for lightly loaded machines. Reducing the heat output allows the system cooling fans to be throttled down or turned off, reducing noise levels, and further decreasing power consumption. The various aspects may also be used for reducing heat in insufficiently cooled systems when the temperature reaches a certain threshold.
While the various aspects are described above for illustrative purposes in terms of processing cores, the aspect methods, systems, and executable instructions may be implemented in any system in which the methods enable recognition of and controlling of frequency or voltage. Further, the operations of scaling the frequency or voltage may be performed on any single or multiprocessor system.
The various aspects may be implemented in a variety of portable or mobile computing devices, an example of which is illustrated in
The various aspects may also be implemented on any of a variety of commercially available server devices, such as the server 1500 illustrated in
The aspects described above may also be implemented within a variety of personal computing devices, such as a laptop computer 1600 as illustrated in
The processing core 1401, 1501, 1601 may be any programmable processor, microprocessor, microcomputer, multi-core processor, or multiple-processor chip that can be configured by software instructions (applications) to perform a variety of functions, including the functions and operations of the various aspects described herein. Typically, software applications may be stored in the internal memory 1402, 1502, 1602 before they are accessed and loaded into the processing core 1401, 1501, 1601. Each processing core 1401, 1501, 1601 may include internal memory sufficient to store the application software instructions. In some computing devices, additional memory chips (e.g., a Secure Data (SD) card) may be plugged into the computing device and coupled to the processing core 1401, 1501, 1601. The internal memory 1402, 1502, 1602 may be a volatile or nonvolatile memory, such as flash memory, or a mixture of both. For the purposes of this description, a general reference to memory refers to all memory accessible by the processing core 1401, 1501, 1601, including internal memory 1402, removable memory plugged into the mobile device, and memory within the processing core 1401.
The processing core 1501, 1601, 1710 may include internal memory sufficient to store the application software instructions. In many devices the internal memory may be a volatile or nonvolatile memory, such as flash memory, or a mixture of both. For the purposes of this description, a general reference to memory refers to memory accessible by the processor 1501, 1601, 1710 including internal memory or removable memory plugged into the device and memory within the processing core 1501, 1601, 1710 itself.
The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various aspects must be performed in the order presented. As will be appreciated by one of skill in the art the order of steps in the foregoing aspects may be performed in any order. Words such as “thereafter,” “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles “a,” “an” or “the” is not to be construed as limiting the element to the singular.
The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The hardware used to implement the various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a multiprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a multiprocessor, a plurality of multiprocessors, one or more multiprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.
In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more processor-executable instructions or code on a non-transitory computer-readable storage medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a tangible or non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may be any available storage media that may be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above also can be included within the scope of non-transitory computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory machine readable medium and/or non-transitory computer-readable medium, which may be incorporated into a computer program product.
The preceding description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.
This application is a continuation-in-part of U.S. patent application Ser. No. 12/944,467, entitled “System and Method for Controlling Central Processing Unit Power with Guaranteed Transient Deadlines” filed Nov. 11, 2010, which claims the benefit of priority to U.S. Provisional Application No. 61/286,991 entitled “System and Method of Dynamically Controlling Power in a Central Processing Unit” filed Dec. 16, 2009, both of which are incorporated by reference in their entirety. The present application is related to, and incorporates by reference, U.S. patent application Ser. No. 12/944,140 entitled “System And Method For Controlling Central Processing Unit Power Based On Inferred Workload Parallelism,” by Rychlik et al.; U.S. patent application Ser. No. 12/944,202 entitled “System and Method for Controlling Central Processing Unit Power in a Virtualized System,” by Rychlik et al.; U.S. patent application Ser. No. 12/944,321 entitled “System and Method for Asynchronously and Independently Controlling Core Clocks in a Multicore Central Processing Unit,” by Rychlik et al.; U.S. patent application Ser. No. 12/944,378 entitled “System and Method for Controlling Central Processing Unit Power with Reduced Frequency Oscillations,” by Thomson et al.; U.S. patent application Ser. No. 12/944,561 entitled “System and Method for Controlling Central Processing Unit Power With Guaranteed Steady State Deadlines,” by Thomson et al.; and U.S. patent application Ser. No. 12/944,564 entitled “System and Method for Dynamically Controlling a Plurality of Cores in a Multicore Central Processing Unit based on Temperature,” by Sur et al.
| Number | Date | Country | |
|---|---|---|---|
| 61286991 | Dec 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12944467 | Nov 2010 | US |
| Child | 13669043 | US |
