US20140310550A1 - Pcie device power state control - Google Patents
Pcie device power state control Download PDFInfo
- Publication number
- US20140310550A1 US20140310550A1 US13/976,545 US201113976545A US2014310550A1 US 20140310550 A1 US20140310550 A1 US 20140310550A1 US 201113976545 A US201113976545 A US 201113976545A US 2014310550 A1 US2014310550 A1 US 2014310550A1
- Authority
- US
- United States
- Prior art keywords
- chipset
- idle
- power state
- state
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3234—Power saving characterised by the action undertaken
- G06F1/325—Power saving in peripheral device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
- G06F1/3215—Monitoring of peripheral devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3234—Power saving characterised by the action undertaken
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Definitions
- Power management for computing platforms is a subject of great concern. It is a major focus in the design and operation of computing platforms, systems and sub-systems. Ideally, devices and components should not operate at a higher level of activity than absolutely required. However, system and devices may not, for example, be fully aware of the present and/or future operational states of the components to which they are connected. In some aspects, software embodied techniques have been proposed to manage the power states of some computing platforms. A disadvantage in some such systems is that the software must be executing in order to manage the power. Thus, the running of the software may itself prevent the system from entering into a lower idle power state.
- FIG. 1 is a block diagram of a system compatible with some embodiments herein.
- FIG. 2 is a flow diagram of a process, in accordance with an embodiment.
- FIG. 3 is a flow diagram of a sequence of events, in accordance with one embodiment.
- FIG. 4 is an illustrative depiction of a power state table, in accordance with one embodiment.
- references in the specification to “one embodiment”, “some embodiments”, “an embodiment”, “an example embodiment”, “an instance”, “some instances” indicate that the embodiment described may include a particular feature, structure, or characteristic, but that every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
- Embodiments herein may be implemented in hardware, firmware, software, or any combinations thereof. Embodiments may also be implemented as executable instructions stored on a machine-readable medium that may be read and executed by one or more processors.
- a machine-readable storage medium may include any tangible non-transitory mechanism for storing information in a form readable by a machine (e.g., a computing device).
- a machine-readable storage medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; and electrical and optical forms of signals.
- firmware, software, routines, and instructions may be described herein as performing certain actions, it should be appreciated that such descriptions are merely for convenience and that such actions are in fact result from computing devices, processors, controllers, and other devices executing the firmware, software, routines, and instructions.
- the present disclosure relates, in some aspects, to a control scheme or algorithm for dynamically controlling a power state of a device connected to a platform based on the power state of the platform.
- the device may be a PCIE (Peripheral Component Interconnect Express) device connected to an end point of a PCIE bus, under the control of a core logic chipset (also referred to herein as “core logic” and “chipset”).
- core logic also referred to herein as “core logic” and “chipset”.
- Some embodiments herein provide a mechanism to manage the power of the PCIE device based on the power state of the platform, under the control of the chipset and within the operational constraints of the PCIE device, the chipset, and other devices, (e.g., internal and external to the chipset).
- device 110 may be any endpoint connected device compatible with the bus 115 protocol.
- Device 110 may be one or more devices.
- concepts and aspects of the present disclosure may be applicable to platform other than those particularly referenced, shown, or discussed herein.
- Process 200 is a flow diagram of a process 200 related to one embodiment of a platform power management method, algorithm, system, and apparatus.
- a chipset e.g., chipset 105
- the power state information may be received as the result of the device advertising its power state capabilities, whether in response to a solicitation or request for such information from the chipset, the chipset requesting such information, as part of a “boot” process, etc.
- the power state information may be accumulated, stored, or persisted for future reference by the chipset.
- the chipset determines an idle power state for the device.
- the determined idle power state may consider and be based, at least in part, on the power state information gathered by the chipset at operation 205 .
- the idle power state determined for the device at operation 210 may consider additional factors other than the device's power capabilities.
- the chipset may consider, for example, operational parameters of the chipset itself as well desired performance goals.
- the chipset may direct the connected device to enter the determined power state.
- the device may receive an indication of the determined idle power state and enter such an idle power state at a next available opportunity.
- the information provided to the device regarding the determined idle power state may include an indication of the power state of the chipset.
- the connected device may make its own state transitions with confidence knowing the state of the chipset (i.e., platform).
- the device may enter the determined idle power state at a next idle period or at all future idle periods unless directed otherwise.
- the core logic and the device may be returned to an active state. Operation 220 may also be managed under the control of the chipset.
- control scheme and methods disclosed herein may be strictly controlled by hardware.
- FIG. 3 is a flow diagram 300 of a sequence of operations occurring between a chipset at 302 and a PCIE device at 304 .
- the device communicates its idle state capabilities to the core logic at 305 .
- the chipset may receive other platform related information.
- the chipset may use the received information, all or parts thereof, to determine or predict how long it can expect to be idle, including expectations on exit latency.
- the core logic may predict how deep of an idle state it can expect to be in a next idle transition.
- FIG. 4 is an illustrative example of power state information for the device connected at 304 .
- the power state information may be captured in a table. It is noted however that any data structure may be used to contain or at least reference the device's power state parameters and values.
- the example of FIG. 4 details the idle states the device is capable of entering, as well as latency and power parameter values corresponding to the idle states.
- D0 refers to an active state
- states D0i1 and D0i2 refer to a light and a deeper idle state, respectively.
- the core logic can inform the connected device to enter a lighter or deeper idle state (e.g., D0i1 and D0i2) that is supported by the device. That is, the core logic may provide guidance to the device regarding the idle power state(s) it should enter based, at least in part, the state of the chipset.
- a lighter or deeper idle state e.g., D0i1 and D0i2
- the device is armed to enter one of the idle states that it supports, D0i1 and D0i2, upon the next idle period by a communication from the core logic.
- this guiding of the device of which idle state to enter may operate to inform the device to prepare for an idle state transition. Such preparing may involve the device “cleaning up” and concluding other operations.
- the platform has decided that it is in or entering an idle state, defined by all cores and activity generators coalescing.
- a signal for example, OBFF Active to Idle, is sent to the external device (and internal devices in some embodiments) to indicate the platform desires to enter an idle state.
- the device may know that it should coalesce the activities it is generating, and that it is safe for it (i.e., the device) to enter into the one of the idle states determined and selected by the core logic.
- the platform core logic expects to be idle for a certain period of time, as illustrated at 325 .
- the core logic also knows the device recovery latency from the information received from the device and stored for use/reference by the chipset.
- the core logic may cause the system to “warm up” and activate in advance of the device exiting the idle state and (potentially) needing platform resources. In some aspects, this “warming up” operation may work to minimize software latency by not adding to it.
- the platform informs the device that is intends to exit the idle state.
- the device may then enter an active state as shown at 330 . Thereafter, the device may resume DMA (and other) transactions.
- a process in accordance herewith may include the selection of idle states for the device based, at least in part, on the device recovery latency.
- the operations and processes herein are implemented in hardware. This is in contrast to OS and other software directed means.
- the present disclosure may also be contrasted with link state power management protocols where a physical connection or link between end points is used, as opposed to the present disclosure that directly manages and controls the operation of the core logic and the device(s).
- the power management scheme herein is independent of a communication link state status.
- All systems and processes discussed herein may be embodied in program code stored on one or more computer-readable media.
- Such media may include, for example, a floppy disk, a CD-ROM, a DVD-ROM, one or more types of “discs”, magnetic tape, a memory card, a flash drive, a solid state drive, and solid state Random Access Memory (RAM) or Read Only Memory (ROM) storage units.
- RAM Random Access Memory
- ROM Read Only Memory
Abstract
Description
- Power management for computing platforms is a subject of great concern. It is a major focus in the design and operation of computing platforms, systems and sub-systems. Ideally, devices and components should not operate at a higher level of activity than absolutely required. However, system and devices may not, for example, be fully aware of the present and/or future operational states of the components to which they are connected. In some aspects, software embodied techniques have been proposed to manage the power states of some computing platforms. A disadvantage in some such systems is that the software must be executing in order to manage the power. Thus, the running of the software may itself prevent the system from entering into a lower idle power state.
- Aspects of the present disclosure herein are illustrated by way of example and not by way of limitation in the accompanying figures. For purposes related to simplicity and clarity of illustration rather than limitation, aspects illustrated in the figures are not necessarily drawn to scale. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.
-
FIG. 1 is a block diagram of a system compatible with some embodiments herein. -
FIG. 2 is a flow diagram of a process, in accordance with an embodiment. -
FIG. 3 is a flow diagram of a sequence of events, in accordance with one embodiment. -
FIG. 4 is an illustrative depiction of a power state table, in accordance with one embodiment. - The disclosure herein provides numerous specific details such regarding a system for implementing various processes and operations. However, it will be appreciated by one skilled in the art(s) related hereto that embodiments of the present disclosure may be practiced without such specific details. Thus, in some instances aspects such as control mechanisms and full software instruction sequences have not been shown in detail in order not to obscure other aspects of the present disclosure. Those of ordinary skill in the art will be able to implement appropriate functionality without undue experimentation given the included descriptions herein.
- References in the specification to “one embodiment”, “some embodiments”, “an embodiment”, “an example embodiment”, “an instance”, “some instances” indicate that the embodiment described may include a particular feature, structure, or characteristic, but that every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
- Some embodiments herein may be implemented in hardware, firmware, software, or any combinations thereof. Embodiments may also be implemented as executable instructions stored on a machine-readable medium that may be read and executed by one or more processors. A machine-readable storage medium may include any tangible non-transitory mechanism for storing information in a form readable by a machine (e.g., a computing device). In some aspects, a machine-readable storage medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; and electrical and optical forms of signals. While firmware, software, routines, and instructions may be described herein as performing certain actions, it should be appreciated that such descriptions are merely for convenience and that such actions are in fact result from computing devices, processors, controllers, and other devices executing the firmware, software, routines, and instructions.
- The present disclosure relates, in some aspects, to a control scheme or algorithm for dynamically controlling a power state of a device connected to a platform based on the power state of the platform. In some embodiments, the device may be a PCIE (Peripheral Component Interconnect Express) device connected to an end point of a PCIE bus, under the control of a core logic chipset (also referred to herein as “core logic” and “chipset”). Some embodiments herein provide a mechanism to manage the power of the PCIE device based on the power state of the platform, under the control of the chipset and within the operational constraints of the PCIE device, the chipset, and other devices, (e.g., internal and external to the chipset).
FIG. 1 is a simplified block diagram of achipset 105 interconnected with aPCIE device 110. In some embodiments,device 110 may be any endpoint connected device compatible with thebus 115 protocol.Device 110 may be one or more devices. In some embodiments, concepts and aspects of the present disclosure may be applicable to platform other than those particularly referenced, shown, or discussed herein. -
Process 200 is a flow diagram of aprocess 200 related to one embodiment of a platform power management method, algorithm, system, and apparatus. Atoperation 205, a chipset (e.g., chipset 105) may receive information including the power state capabilities of a platform connected device (e.g., PCIE device 110). The power state information may be received as the result of the device advertising its power state capabilities, whether in response to a solicitation or request for such information from the chipset, the chipset requesting such information, as part of a “boot” process, etc. The power state information may be accumulated, stored, or persisted for future reference by the chipset. - At
operation 210, the chipset determines an idle power state for the device. The determined idle power state may consider and be based, at least in part, on the power state information gathered by the chipset atoperation 205. In some embodiments, the idle power state determined for the device atoperation 210 may consider additional factors other than the device's power capabilities. In some instances, the chipset may consider, for example, operational parameters of the chipset itself as well desired performance goals. - At
operation 215 the chipset may direct the connected device to enter the determined power state. In some embodiments, the device may receive an indication of the determined idle power state and enter such an idle power state at a next available opportunity. In some embodiments, the information provided to the device regarding the determined idle power state may include an indication of the power state of the chipset. Based on the power state of the chipset as reported from the chipset, the connected device may make its own state transitions with confidence knowing the state of the chipset (i.e., platform). In some embodiments, the device may enter the determined idle power state at a next idle period or at all future idle periods unless directed otherwise. - At
operation 220, the core logic and the device may be returned to an active state.Operation 220 may also be managed under the control of the chipset. - In some aspects, it is noted that the control scheme and methods disclosed herein may be strictly controlled by hardware.
-
FIG. 3 is a flow diagram 300 of a sequence of operations occurring between a chipset at 302 and a PCIE device at 304. According toFIG. 3 , the device communicates its idle state capabilities to the core logic at 305. In this instance, as provide by the DMA Capability structure of the PCIE standard. In addition to collecting or gathering the power state capabilities of the device, the chipset may receive other platform related information. The chipset may use the received information, all or parts thereof, to determine or predict how long it can expect to be idle, including expectations on exit latency. The core logic may predict how deep of an idle state it can expect to be in a next idle transition. -
FIG. 4 is an illustrative example of power state information for the device connected at 304. As shown, the power state information may be captured in a table. It is noted however that any data structure may be used to contain or at least reference the device's power state parameters and values. The example ofFIG. 4 details the idle states the device is capable of entering, as well as latency and power parameter values corresponding to the idle states. In this example, D0 refers to an active state and states D0i1 and D0i2 refer to a light and a deeper idle state, respectively. - Based on the gathered or accumulated device power state and platform information, the core logic can inform the connected device to enter a lighter or deeper idle state (e.g., D0i1 and D0i2) that is supported by the device. That is, the core logic may provide guidance to the device regarding the idle power state(s) it should enter based, at least in part, the state of the chipset.
- At
operation 310, the device is armed to enter one of the idle states that it supports, D0i1 and D0i2, upon the next idle period by a communication from the core logic. In some aspects, this guiding of the device of which idle state to enter may operate to inform the device to prepare for an idle state transition. Such preparing may involve the device “cleaning up” and concluding other operations. - At
operation 315, the platform has decided that it is in or entering an idle state, defined by all cores and activity generators coalescing. A signal, for example, OBFF Active to Idle, is sent to the external device (and internal devices in some embodiments) to indicate the platform desires to enter an idle state. - At this juncture of the process, the device may know that it should coalesce the activities it is generating, and that it is safe for it (i.e., the device) to enter into the one of the idle states determined and selected by the core logic.
- The platform core logic expects to be idle for a certain period of time, as illustrated at 325. In some aspects, the core logic also knows the device recovery latency from the information received from the device and stored for use/reference by the chipset.
- In some aspects, the core logic may cause the system to “warm up” and activate in advance of the device exiting the idle state and (potentially) needing platform resources. In some aspects, this “warming up” operation may work to minimize software latency by not adding to it.
- At
operation 320, the platform informs the device that is intends to exit the idle state. The device may then enter an active state as shown at 330. Thereafter, the device may resume DMA (and other) transactions. - It is seen that the present disclosure provides a mechanism to have devices enter a low (e.g., idle) power state in an orderly and sequenced manner. As illustrated by the foregoing discussion, a process in accordance herewith may include the selection of idle states for the device based, at least in part, on the device recovery latency.
- In some embodiments, the operations and processes herein are implemented in hardware. This is in contrast to OS and other software directed means. The present disclosure may also be contrasted with link state power management protocols where a physical connection or link between end points is used, as opposed to the present disclosure that directly manages and controls the operation of the core logic and the device(s). In some aspects, the power management scheme herein is independent of a communication link state status.
- All systems and processes discussed herein may be embodied in program code stored on one or more computer-readable media. Such media may include, for example, a floppy disk, a CD-ROM, a DVD-ROM, one or more types of “discs”, magnetic tape, a memory card, a flash drive, a solid state drive, and solid state Random Access Memory (RAM) or Read Only Memory (ROM) storage units. Embodiments are therefore not limited to any specific combination of hardware and software.
- Embodiments have been described herein solely for the purpose of illustration. Persons skilled in the art will recognize from this description that embodiments are not limited to those described, but may be practiced with modifications and alterations limited only by the spirit and scope of the appended claims.
Claims (18)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2011/068096 WO2013101180A1 (en) | 2011-12-30 | 2011-12-30 | Pcie device power state control |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140310550A1 true US20140310550A1 (en) | 2014-10-16 |
US9778720B2 US9778720B2 (en) | 2017-10-03 |
Family
ID=48698414
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/976,545 Expired - Fee Related US9778720B2 (en) | 2011-12-30 | 2011-12-30 | PCIE device power state control |
Country Status (5)
Country | Link |
---|---|
US (1) | US9778720B2 (en) |
DE (1) | DE112011106055T5 (en) |
IN (1) | IN2014CN04322A (en) |
TW (1) | TWI609268B (en) |
WO (1) | WO2013101180A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160066267A1 (en) * | 2014-09-02 | 2016-03-03 | Apple Inc. | Power adaptation during communication for improved margin |
WO2017023289A1 (en) * | 2015-07-31 | 2017-02-09 | Hewlett Packard Enterprise Development Lp | Determining power state support |
WO2023024619A1 (en) * | 2021-08-27 | 2023-03-02 | 超聚变数字技术有限公司 | Method for managing peripheral component interconnect express (pcie) device, and related apparatus |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9501441B2 (en) | 2013-12-16 | 2016-11-22 | Dell Products, Lp | Mechanism to boot multiple hosts from a shared PCIe device |
TWI559148B (en) * | 2015-05-11 | 2016-11-21 | 廣達電腦股份有限公司 | Automatic hardware recovery method and automatic hardware recovery system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5919264A (en) * | 1997-03-03 | 1999-07-06 | Microsoft Corporation | System and method for using data structures to share a plurality of power resources among a plurality of devices |
US20030105983A1 (en) * | 2001-12-03 | 2003-06-05 | Brakmo Lawrence Sivert | Power reduction in computing devices using micro-sleep intervals |
US20050091549A1 (en) * | 2003-10-28 | 2005-04-28 | Arthur Wu | Universal serial bus with power-saving mode and operating method thereof |
US20050235171A1 (en) * | 2003-09-02 | 2005-10-20 | Kabushiki Kaisha Toshiba | Electronic device with serial ATA interface and power saving method for serial ATA buses |
US20090249103A1 (en) * | 2008-03-31 | 2009-10-01 | Jeyaseelan Jaya L | Platform power management based on latency guidance |
US7793120B2 (en) * | 2007-01-19 | 2010-09-07 | Microsoft Corporation | Data structure for budgeting power for multiple devices |
US20110138206A1 (en) * | 2007-09-12 | 2011-06-09 | Nokia Corporation | Power Management Method and Apparatus |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5754869A (en) | 1994-10-04 | 1998-05-19 | Intel Corporation | Method and apparatus for managing power consumption of the CPU and on-board system devices of personal computers |
US8495403B2 (en) | 2008-12-31 | 2013-07-23 | Intel Corporation | Platform and processor power management |
US8635469B2 (en) | 2009-12-22 | 2014-01-21 | Intel Corporation | Method and apparatus for I/O devices assisted platform power management |
US8185758B2 (en) * | 2011-06-30 | 2012-05-22 | Intel Corporation | Method and system for determining an energy-efficient operating point of a platform |
-
2011
- 2011-12-30 WO PCT/US2011/068096 patent/WO2013101180A1/en active Application Filing
- 2011-12-30 US US13/976,545 patent/US9778720B2/en not_active Expired - Fee Related
- 2011-12-30 IN IN4322CHN2014 patent/IN2014CN04322A/en unknown
- 2011-12-30 DE DE112011106055.6T patent/DE112011106055T5/en not_active Ceased
-
2012
- 2012-12-13 TW TW101147171A patent/TWI609268B/en not_active IP Right Cessation
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5919264A (en) * | 1997-03-03 | 1999-07-06 | Microsoft Corporation | System and method for using data structures to share a plurality of power resources among a plurality of devices |
US20030105983A1 (en) * | 2001-12-03 | 2003-06-05 | Brakmo Lawrence Sivert | Power reduction in computing devices using micro-sleep intervals |
US20050235171A1 (en) * | 2003-09-02 | 2005-10-20 | Kabushiki Kaisha Toshiba | Electronic device with serial ATA interface and power saving method for serial ATA buses |
US20050091549A1 (en) * | 2003-10-28 | 2005-04-28 | Arthur Wu | Universal serial bus with power-saving mode and operating method thereof |
US7793120B2 (en) * | 2007-01-19 | 2010-09-07 | Microsoft Corporation | Data structure for budgeting power for multiple devices |
US20110138206A1 (en) * | 2007-09-12 | 2011-06-09 | Nokia Corporation | Power Management Method and Apparatus |
US20090249103A1 (en) * | 2008-03-31 | 2009-10-01 | Jeyaseelan Jaya L | Platform power management based on latency guidance |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160066267A1 (en) * | 2014-09-02 | 2016-03-03 | Apple Inc. | Power adaptation during communication for improved margin |
WO2017023289A1 (en) * | 2015-07-31 | 2017-02-09 | Hewlett Packard Enterprise Development Lp | Determining power state support |
WO2023024619A1 (en) * | 2021-08-27 | 2023-03-02 | 超聚变数字技术有限公司 | Method for managing peripheral component interconnect express (pcie) device, and related apparatus |
Also Published As
Publication number | Publication date |
---|---|
TW201346578A (en) | 2013-11-16 |
IN2014CN04322A (en) | 2015-09-04 |
DE112011106055T5 (en) | 2014-09-18 |
US9778720B2 (en) | 2017-10-03 |
TWI609268B (en) | 2017-12-21 |
WO2013101180A1 (en) | 2013-07-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9778720B2 (en) | PCIE device power state control | |
RU2599967C2 (en) | Application lifecycle management | |
US9250684B1 (en) | Dynamic power capping of a subset of servers when a power consumption threshold is reached and allotting an amount of discretionary power to the servers that have power capping enabled | |
KR101864980B1 (en) | Virtual machine power management | |
EP3091434B1 (en) | Chip starting method, multi-core processor chip and storage medium | |
US20180120917A1 (en) | Aggregated electronic device power management | |
US20190095250A1 (en) | Application program management method and device | |
DE102013104329B4 (en) | Task allocation in large and small cores | |
US20130111226A1 (en) | Controlling A Turbo Mode Frequency Of A Processor | |
US20130097433A1 (en) | Systems and methods for dynamic resource management in solid state drive system | |
US20120166731A1 (en) | Computing platform power management with adaptive cache flush | |
EP3376379A1 (en) | Task management methods and system, and computer storage medium | |
KR20170021864A (en) | Methods and apparatus to manage jobs that can and cannot be suspended when there is a change in power allocation to a distributed computer system | |
CA2636908A1 (en) | System and method for portable power source management | |
US9898329B1 (en) | Flexible processor association for virtual machines | |
CN103916374B (en) | Service gray scale dissemination method and device | |
US9047088B2 (en) | Multiprocessor system and method of controlling power | |
US9746897B2 (en) | Method for controlling a multi-core central processor unit of a device establishing a relationship between device operational parameters and a number of started cores | |
CN107624181B (en) | Virtual machine management method and apparatus including idling and scheduling of virtual processors | |
US10146623B2 (en) | Indicating rebuild state of storage devices | |
CN110362448A (en) | A kind of GPU management-control method and relevant apparatus | |
US20160077882A1 (en) | Scheduling system, scheduling method, and recording medium | |
WO2018115958A2 (en) | Method for operating a device having a switchable power saving mode for reducing its power consumption | |
US8661201B2 (en) | Systems and methods for managing destage conflicts | |
CN116016175A (en) | OTA (over the air) upgrading method and device for automatic driving operation vehicle |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTEL CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KUMAR, ANIL K.;CRAWFORD, JOHN H.;DIEFENBAUGH, PAUL S.;SIGNING DATES FROM 20130326 TO 20140610;REEL/FRAME:033079/0090 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20211003 |