The present application claims priority to U.S. Provisional Patent Application Ser. No. 61/287,011, entitled SYSTEM AND METHOD OF DYNAMICALLY CONTROLLING A PLURALITY OF CORES IN A MULTICORE CENTRAL PROCESSING UNIT, filed on Dec. 16, 2009.
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., filed concurrently. The present application is related to, and incorporates by reference, 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., filed concurrently. The present application is related to, and incorporates by reference, 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., filed concurrently. The present application is related to, and incorporates by reference, 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., filed concurrently. The present application is related to, and incorporates by reference, U.S. patent application Ser. No. 12/944,467, entitled SYSTEM AND METHOD FOR CONTROLLING CENTRAL PROCESSING UNIT POWER WITH GUARANTEED TRANSIENT DEADLINES, by Thomson et al., filed concurrently. The present application is related to, and incorporates by reference, 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., filed concurrently.
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.
In the figures, like reference numerals refer to like parts throughout the various views unless otherwise indicated.
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
The PCD 320 may further include a temperature sensor 382 that may be used to sense a die temperature associated with the PCD 320. In other words, the temperature sensor 382 may act as a means for sensing a die temperature associated with the PCD 320.
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, temperature sensor 382, or a combination thereof may serve as a means for executing one or more of the method steps described herein in order to control a multicore central processing unit based on temperature.
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.
In a particular aspect, the parallelism monitor 440 may be a software program that monitors the run queues 424, 426, 428 in the scheduler 422. Each run queue 424, 426, 428 (aka, ready-to-run queue) may include a list of current tasks, threads, or a combination thereof that are available for scheduling on one or more cores 410, 412, 414. Some multicore systems may only have a single ready-to-run queue. Other multicore systems may have multiple ready-to-run queues. Regardless, of the number of ready-to-run queues, at any instant in time, the total number of tasks, threads, or a combination thereof waiting on these queues, plus a number of tasks, threads, or a combination thereof actually running, may be an approximation for the degree of parallelism in the workload.
Referring to
At block 504, a die temperature may be monitored. Further, at block 506, a power controller may determine a degree of parallelism in the workload associated with the cores.
Moving to block 508, the power controller may independently power the cores up or down based on the degree of workload parallelism, the die temperature, or a combination thereof. Next, at decision 510, the power controller may determine whether the device is powered off. If the device is powered off, the method may end. Otherwise, if the device remains powered on, the method 500 may return to block 504 and the method 500 may continue as described.
Referring to
Moving to decision 606, a core controller may determine whether the die temperature is equal to a critical condition. For example, the critical condition may be threshold temperature above which operation of the device may begin to break down due to temperature issues.
At decision 606, if the die temperature does not equal a critical condition, the method 600 may return to block 602 and the method 600 may continue as described herein. Otherwise, if the die temperature does equal a critical condition, the method 600 may move to decision 608 and the core controller may determine whether a second core is dormant, e.g., the second core may be a CPU1 (the first core may be CPU0).
If the second core is not dormant, i.e., CPU1 is active and executing tasks and threads, the method 600 may proceed to block 610. At block 610, the frequency of the first core, CPU0, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. In other words, the core controller may reduce the frequency of the second core one incremental step without going below an optimal frequency, Fopt. The incremental step may be one hundred megahertz (100 MHz) or less. Further, the incremental step may be fifty megahertz (50 MHz) or less. From block 610, the method 600 may return to block 602 and the method 600 may continue as described.
Returning to decision 608, if CPU1 is dormant, i.e., CPU1 is powered off, the method 600 may proceed to decision 612. At decision 612, a controller may determine whether a degree of parallelism meets a condition. Specifically, the controller may determine whether the degree of parallelism is greater than a predetermined threshold indicating that there is enough parallelism in the system to warrant the operation of a second core, CPU1.
At decision 612, if the degree of parallelism does not meet the condition, the method may move to block 614 and the frequency of the first core, CPU0, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. In other words, the core controller may reduce the frequency of the second core one incremental step without going below an optimal frequency, Fopt. Thereafter, the method 600 may return to block 602 and the method 600 may continue as described herein.
Returning to decision 612, if the degree of parallelism meets the condition, the method may proceed to block 616 and the second CPU, CPU1, may be turned on. Thereafter, at block 618, the frequency of the second core, CPU1, may be set to an optimal frequency, Fopt. Also, at block 618, the frequency of the first core, CPU0, may be set to the maximum of the current frequency of the first core minus the optimal frequency, Fopt, or the optimal frequency, Fopt. For example, if CPU0 is operating at one thousand megahertz (1000 MHz) and CPU1 is powered on to an optimal frequency of six hundred megahertz (600 MHz), the frequency of CPU0 may be changed to six hundred megahertz (600 MHz) because 1000 MHz minus 600 MHz is equal to four hundred megahertz (400 MHz) and 600 MHz (the optimal frequency, Fopt) is greater than 400 MHz (the result of the subtraction operation).
In another example, if CPU0 is operating at one thousand four hundred megahertz (1400 MHz) and CPU1 is powered on to an optimal frequency of six hundred megahertz (600 MHz), the frequency of CPU0 may be changed to eight hundred megahertz (800 MHz) because 1400 MHz minus 600 MHz is equal to eight hundred megahertz (800 MHz) and 800 MHz (the result of the subtraction operation) is greater than 600 MHz (the optimal frequency, Fop).
Moving to decision 620, the controller may determine whether there is sustained parallelism in the system. In other words, the controller may determine whether the degree of parallelism in the system meets a condition for at least a predetermined amount of time. The condition may be a threshold value of parallelism and if the parallelism in the system is greater than the threshold value, the condition may be considered met. At decision 620, if the parallelism is sustained, the method 600 may return to block 602 and the method 600 may continue as described herein.
Referring now to
Moving to decision 706, a core controller may determine whether the die temperature is equal to a critical condition. For example, the critical condition may be threshold temperature above which operation of the device may begin to break down due to temperature issues.
At decision 706, if the die temperature does not equal a critical condition, the method 700 may return to block 702 and the method 700 may continue as described herein. Otherwise, if the die temperature does equal a critical condition, the method 700 may move to decision 708 and the core controller may determine whether a second core is dormant, e.g., the second core may be a CPU1 (the first core may be CPU0). If the second core is not dormant, the method 700 may proceed to decision 802 of
Otherwise, if CPU1 is dormant, i.e., CPU1 is powered off, the method 700 may proceed to decision 710. At decision 710, a controller may determine whether a degree of parallelism meets a condition. Specifically, the controller may determine whether the degree of parallelism is greater than a predetermined threshold indicating that there is enough parallelism in the system to warrant the operation of a second core, CPU1.
At decision 710, if the degree of parallelism does not meet the condition, the method may move to block 712 and the frequency of the first core, CPU0, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. In other words, the core controller may reduce the frequency of the second core one incremental step without going below an optimal frequency, Fopt. Thereafter, the method 700 may return to block 702 and the method 700 may continue as described herein.
Returning to decision 710, if the degree of parallelism meets the condition, the method may proceed to block 714 and the second CPU, CPU1, may be turned on. Thereafter, at block 716, the frequency of the second core, CPU1, may be set to an optimal frequency, Fopt. Further, at block 716, the frequency of the first core, CPU0, may be set to the maximum of the current frequency of the first core minus the optimal frequency, Fopt, or the optimal frequency, Fopt.
Moving to decision 718, the controller may determine whether there is sustained parallelism in the system. In other words, the controller may determine whether the degree of parallelism in the system meets a condition for at least a predetermined amount of time warranting the continued operation of both cores. The condition may be a threshold value of parallelism and if the parallelism in the system is greater than the threshold value, the condition may be considered met. At decision 718, if the parallelism is sustained, the method 700 may return to block 702 and the method 700 may continue as described herein.
Returning to decision 718, if the parallelism is not sustained, the method 700 may proceed to block 720 and the second core, CPU1, may be turned off. Thereafter, the method 700 may return to block 702 and the method 700 may continue as described herein.
Returning to decision 708, if the second core, CPU1, is not dormant, the method 700 may move to decision 802. At decision 802, the core controller may determine whether an Nth core, CPUN is dormant. If the Nth core is not dormant, the method 700 may proceed to block 804. At block 804, the frequency of the first core, CPU0, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. In other words, the core controller may reduce the frequency of the second core one incremental step without going below an optimal frequency, Fopt. Further, the frequency of the second core, CPU1, may be set, or otherwise moved to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. Also, the frequency of the Nth core, CPUN, may be set, or otherwise moved to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. From block 804, the method 700 may return to block 702 of
Returning to decision 802, if CPUN is dormant, the method 700 may proceed to decision 806. At decision 806, a controller may determine whether a degree of parallelism meets a condition. Specifically, the controller may determine whether the degree of parallelism is greater than a predetermined threshold indicating that there is enough parallelism in the system to warrant the operation of an Nth core, CPUN.
At decision 806, if the degree of parallelism does not meet the condition, the method may move to block 808 and the frequency of the first core, CPU0, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. In other words, the core controller may reduce the frequency of the second core one incremental step without going below an optimal frequency, Fopt. Also, at block 808, the frequency of the second core, CPU1, may be set, or otherwise moved, to the maximum of lowering the frequency of the first core one incremental step and an optimal frequency, Fopt. Thereafter, the method 700 may return to block 702 of
Returning to decision 806, if the degree of parallelism meets the condition, the method may proceed to block 810 and the Nth CPU, CPUN, may be turned on. Thereafter, at block 812, the frequency of the Nth core, CPUN, may be set to an optimal frequency, Fopt. Further, at block 812, the frequency of the first core, CPU0, and the second core, CPU1, may be set to the maximum of the current frequency of the first core minus the optimal frequency, Fopt, or the optimal frequency, Fopt.
Moving to decision 814, the controller may determine whether there is sustained parallelism in the system. In other words, the controller may determine whether the degree of parallelism in the system meets a condition for at least a predetermined amount of time to warrant the operation of N cores. The condition may be a threshold value of parallelism and if the parallelism in the system is greater than the threshold value, the condition may be considered met. At decision 814, if the parallelism is sustained, the method 700 may return to block 702 of
Returning to decision 814, if the parallelism is not sustained, the method 700 may proceed to block 816 and one or more cores may be turned off. Thereafter, the method 700 may return to block 702 of
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, it may be appreciated that dynamic power in a system is proportional to V^2 f, where f is the clock frequency and V represents voltage. Voltage is also positively correlated with frequency. In other words, there exists a minimum voltage for the CPU to run at a given clock frequency. As such, the heat generated at the die roughly proportional to f^3. In certain aspects, it may be possible that when a particular device is assembled, the device may not be able to sufficiently dissipate the heat generated when a CPU core is run at or near its highest frequency.
The system and method disclosed herein provides a way to prevent overheating of a device by exploiting the parallelism in the system and spreading the workload across multiple cores, thereby running each core at much lower frequency. Because of cubic non-linearity in heat generation with respect to clock frequency, running two cores at lower frequencies will result in generating a lot less heat compared to when it is run on a single core, without sacrificing user experience.
In a particular aspect, the degree of parallelism in the workload may be dynamically inferred at task/thread level by monitoring an operating system state. For example, one operating system state that may be monitored is the length of all OS scheduler ready-to-run queues. The scheduler ready-to-run queue is a list of current tasks of threads that are available for scheduling on CPUs.
Using a parallelism monitor, the system may be able to determine whether there is sufficient parallelism in the system at any point of time and whether the parallelism is sustained over a period of time. Both these may be used in the load balancing algorithm described herein.
The load-balancing algorithm disclosed herein may take periodically measured die temperature as one of the inputs. Further, the load-balancing algorithm may compare the die temperature to a threshold temperature, THS, which is the highest temperature still considered safe for proper operation of a handset. In a particular embodiment, THS may be found through experimentation.
In a particular aspect, for each core, there exists a most power efficient voltage and frequency point, Fopt. Fopt may be near the highest frequency level that the minimum operating voltage can sustain. For a homogeneous dual CPU-core based system, both cores running at Fopt may not generate enough heat to take the temperature beyond THS. During operation, the CPU operating frequencies may be incrementally changed and are often a handful of discrete values, typically in steps of 50-100 MHz.
Starting at any point of time, if the temperature sensor ever crosses temperature threshold THS, a controller may check if one core or both cores are running If only one core is running, the controller checks if there is enough parallelism in the system. If there enough parallelism, the controller may bring up the second core at Fopt while reducing the frequency of the first core by the same amount unless doing so would bring the frequency below Fopt. If reducing the frequency of the first core would bring the frequency below Fopt, the controller leaves the first core at Fopt. Again, it may be appreciated that running both cores running at Fopt, may not increase the temperature beyond THS. Spreading the work between two cores may cool down the system without loss of MIPS and harming the user experience.
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 instructions or code on a computer program product such as a machine readable medium, i.e., a non-transitory computer-readable medium. Computer-readable media includes computer storage media that facilitates transfer of a computer program from one place to another. A storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory 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 should also be included within the scope of non-transitory computer-readable media.
Number | Name | Date | Kind |
---|---|---|---|
5644769 | Hasiguti | Jul 1997 | A |
6076171 | Kawata | Jun 2000 | A |
6804632 | Orenstien et al. | Oct 2004 | B2 |
6829713 | Cooper et al. | Dec 2004 | B2 |
6978389 | Jahnke | Dec 2005 | B2 |
7043405 | Orenstien et al. | May 2006 | B2 |
7058824 | Plante et al. | Jun 2006 | B2 |
7107187 | Saghier et al. | Sep 2006 | B1 |
7133806 | Prasad | Nov 2006 | B2 |
7134031 | Flautner | Nov 2006 | B2 |
7219245 | Raghuvanshi | May 2007 | B1 |
7233188 | Takano et al. | Jun 2007 | B1 |
7263457 | White et al. | Aug 2007 | B2 |
7369967 | Washburn et al. | May 2008 | B1 |
7370189 | Fischer et al. | May 2008 | B2 |
7398407 | Jorgenson et al. | Jul 2008 | B2 |
7401240 | Heller, Jr. et al. | Jul 2008 | B2 |
7437581 | Grochowski et al. | Oct 2008 | B2 |
7467291 | Cockroft et al. | Dec 2008 | B1 |
7500124 | Seo | Mar 2009 | B2 |
7543161 | Olszewski et al. | Jun 2009 | B2 |
7669067 | Degenhardt | Feb 2010 | B2 |
7689838 | Srinivasan et al. | Mar 2010 | B2 |
7711966 | Prabhakaran et al. | May 2010 | B2 |
7783906 | Turner et al. | Aug 2010 | B2 |
20020046354 | Ostrom et al. | Apr 2002 | A1 |
20020188877 | Buch | Dec 2002 | A1 |
20030115495 | Rawson, III | Jun 2003 | A1 |
20030177163 | Nomura | Sep 2003 | A1 |
20040225902 | Cesare et al. | Nov 2004 | A1 |
20040254765 | Lee et al. | Dec 2004 | A1 |
20050050373 | Orenstien et al. | Mar 2005 | A1 |
20050102560 | Taketoshi et al. | May 2005 | A1 |
20060036878 | Rothman et al. | Feb 2006 | A1 |
20060123253 | Morgan et al. | Jun 2006 | A1 |
20060149975 | Rotem et al. | Jul 2006 | A1 |
20070033425 | Clark | Feb 2007 | A1 |
20070033526 | Thompson et al. | Feb 2007 | A1 |
20070255929 | Kasahara et al. | Nov 2007 | A1 |
20080005591 | Trautman et al. | Jan 2008 | A1 |
20080028244 | Capps et al. | Jan 2008 | A1 |
20080168287 | Berry et al. | Jul 2008 | A1 |
20080201591 | Hu et al. | Aug 2008 | A1 |
20080310099 | Monferrer et al. | Dec 2008 | A1 |
20090037922 | Herington | Feb 2009 | A1 |
20090049314 | Taha et al. | Feb 2009 | A1 |
20090106576 | Jacobowitz et al. | Apr 2009 | A1 |
20090150695 | Song et al. | Jun 2009 | A1 |
20090150696 | Song et al. | Jun 2009 | A1 |
20090187775 | Ishikawa | Jul 2009 | A1 |
20090217276 | Brenner et al. | Aug 2009 | A1 |
20090230930 | Jain et al. | Sep 2009 | A1 |
20090249347 | Henmi | Oct 2009 | A1 |
20090271646 | Talwar et al. | Oct 2009 | A1 |
20090276642 | Burton et al. | Nov 2009 | A1 |
20100076733 | Kumar et al. | Mar 2010 | A1 |
20100122101 | Naffziger et al. | May 2010 | A1 |
20110023047 | Memik et al. | Jan 2011 | A1 |
20110145559 | Thomson et al. | Jun 2011 | A1 |
20110145615 | Rychlik et al. | Jun 2011 | A1 |
20110145616 | Rychlik et al. | Jun 2011 | A1 |
20110145617 | Thomson et al. | Jun 2011 | A1 |
20110145624 | Rychlik et al. | Jun 2011 | A1 |
20110145824 | Thomson et al. | Jun 2011 | A1 |
20130074085 | Thomson et al. | Mar 2013 | A1 |
20130151879 | Thomson | Jun 2013 | A1 |
Number | Date | Country |
---|---|---|
0098169 | Jan 1984 | EP |
0942363 | Sep 1999 | EP |
1496424 | Jan 2005 | EP |
2445167 | Jul 2008 | GB |
H0351902 | Mar 1991 | JP |
8006681 | Jan 1996 | JP |
H08190535 | Jul 1996 | JP |
H10268963 | Oct 1998 | JP |
H11282695 | Oct 1999 | JP |
2002099433 | Apr 2002 | JP |
2004533674 | Nov 2004 | JP |
2005128937 | May 2005 | JP |
2006011548 | Jan 2006 | JP |
2008059054 | Mar 2008 | JP |
2008117397 | May 2008 | JP |
2008513912 | May 2008 | JP |
2008129846 | Jun 2008 | JP |
2008165798 | Jul 2008 | JP |
2008269249 | Nov 2008 | JP |
2009503728 | Jan 2009 | JP |
2009140157 | Jun 2009 | JP |
2009169858 | Jul 2009 | JP |
2009238024 | Oct 2009 | JP |
2010518525 | May 2010 | JP |
20070049226 | May 2007 | KR |
20090107490 | Oct 2009 | KR |
WO0225414 | Mar 2002 | WO |
WO-02074046 | Sep 2002 | WO |
WO-2004044720 | May 2004 | WO |
WO2005119412 | Dec 2005 | WO |
WO-2006037119 | Apr 2006 | WO |
2007007300 | Jan 2007 | WO |
2008047179 | Apr 2008 | WO |
Entry |
---|
William Stallings, Operating systems internals and design principles, 2005, Pearson, 5th edition, section 3.2. |
Semeraro et al., “Energy-Efficient Processor Design Using Multiple Clock Domains with Dynamic Voltage and Frequency Scaling,” International Symposium on High-Performance Computer Architecture, pp. 0029, Eighth International Symposium on High-Performance Computer architecture (HPCA'02), 2002, Boston, Massachusetts. ISBN: 0-7695-1525-8. |
Wonyoung Kim, Meeta S. Gupta, Gu-Yeon Wei and David Brooks, “System Level Analysis of Fast, Per-Core DVFS using On-Chip Switching Regulators.” IEEE International Symposium on High-Performance Computer Architecture (HPCA), Feb. 2008. |
International Search Report and Written Opinion—PCT/US2010/058075—ISA/EPO—Apr. 27, 2011. |
International Search Report and Written Opinion—PCT/US2010/059535, ISA/EPO—Apr. 28, 2011. |
International Search Report and Written Opinion—PCT/US2010/059560—ISA/EPO—Jun. 15, 2011. |
International Search Report and Written Opinion—PCT/US2010/059562, ISA/EPO—May 27, 2011. |
International Search Report and Written Opinion—PCT/US2010/059538, International Search Authority—European Patent Office—Apr. 7, 2011. |
Compaq et al, “Advanced Configuration and Power Interface Specification”, Compaq Computer Corporation, Intel Cor0poration, Microsoft Corporation, Phoenix Technologies Ltd., Toshiba Corporation, Revision 2.0, Jul. 27, 2000. |
iDebian, CPU frequency scaling in Linux, Jun. 26, 2008, iDebian's Weblog. |
Kanai J, et al., “Statistical Prediction-based Energy-Aware Linux Scheduler for CMP systems”, Proceedings of computer system symposium (IPSJ symposium series), vol. 2008, No. 12, Information Processing Society of Japan, Nov. 5, 2008, pp. 77-86. |
Number | Date | Country | |
---|---|---|---|
20110145605 A1 | Jun 2011 | US |
Number | Date | Country | |
---|---|---|---|
61287011 | Dec 2009 | US |