# Patent

## Title
Controlling operating frequency of a core domain via a non-core domain of a multi-domain processor

## Abstract

In one embodiment, the present invention includes a method for determining that a non-core domain of a multi-domain processor is not operating at a frequency requested by the non-core domain, sending a request from the non-core domain to a power controller to reduce a frequency of a core domain of the multi-domain processor, and responsive to the request, reducing the core domain frequency. Other embodiments are described and claimed.

## Background
BACKGROUND
As technology advances in the semiconductor field, devices such as processors incorporate ever-increasing amounts of circuitry. Over time, processor designs have evolved from a collection of independent integrated circuits (ICs), to a single integrated circuit, to multicore processors that include multiple processor cores within a single IC package. As time goes on, ever greater numbers of cores and related circuitry are being incorporated into processors and other semiconductors.
Multicore processors are being extended to include additional functionality by incorporation of other functional units within the processor. These units share a single power budget. As a result, the higher the frequency at which a core portion of the processor operates, the higher the power consumed by the core portion, leaving lesser power for other portions of the processor. Suitable mechanisms to ensure that these different units have sufficient power do not presently exist.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a flow diagram of a high level method in accordance with one embodiment of the present invention.
FIG. 2 is a flow diagram of a method for dynamic frequency range control of a core domain in accordance with an embodiment of the present invention.
FIG. 3 is a graphical illustration of dynamic frequency range control in accordance with an embodiment of the present invention.
FIG. 4 is a block diagram of a processor in accordance with an embodiment of the present invention.
FIG. 5 is a block diagram of a multi-domain processor in accordance with another embodiment of the present invention.
FIG. 6 is a block diagram of a system in accordance with an embodiment of the present invention.



DETAILED DESCRIPTION
In various embodiments, a non-core domain of a multi-domain processor can cause a core domain's frequency to be reduced. This frequency reduction can be by way of control of a maximum allowable frequency at which the core domain can run (commonly referred to as a maximum turbo frequency) as well as control of a guaranteed frequency at which the core domain can run. In this way, a non-core domain (or software, firmware, or logic of such domain) can override a setting or request of an operating system (OS) or other scheduler for higher core frequencies. Thus this non-core domain entity can dynamically alter the range of frequencies at which a core domain is enabled to run, and greater power and/or thermal budget can be allocated to the non-core domain. Although described herein with regard to a multi-domain processor including a core domain having one or more processor cores and a non-core domain that in an illustrative embodiment is a graphics engine, understand the scope of the present invention is not limited in this regard and in other embodiments more than two domains can be present, each of which can have dynamically alterable frequency ranges.
By providing this non-core domain control, a common budget for a processor, e.g., a shared power budget, can be more efficiently used. In general, an OS determines an operating frequency for a core domain based on core utilization only. Other domains however may not benefit from a selected operating frequency for the core domain. For example, a graphics domain may not benefit from a given core operating frequency. For a particular graphics workload, a graphics driver, which can execute within the core domain, can perform a so-called spin loop to check to determine whether a parceled amount of work given to the graphics domain has completed. This spin loop consumes power as it iteratively checks to determine whether the work has completed. By always running, this driver can thus increase core utilization and cause an OS to select a relatively high operating frequency at which to run the core domain. Assuming that this type of scenario causes the core domain to enter into a greater than guaranteed frequency such as a given turbo frequency, due to the common power (and thermal) budget, it is possible that operation of the graphics domain that is actually performing the major workload of the processor in this illustration can be constrained. Instead using embodiments of the present invention, the graphics domain can aid in controlling operating frequency of the core domain. In this way, a power budget can be more efficiently shared between core and non-core domains.
Note that the operating frequency for a core domain selected by the OS can be in accordance with an OS-based power control implementation such as the Advanced Configuration and Platform Interface (ACPI) standard (e.g., Rev. 3.0b, published Oct. 10, 2006). According to ACPI, a processor can operate at various performance states or levels, namely from P0 to PN. In general, the P1 performance state may correspond to the highest guaranteed performance state that can be requested by the OS. In addition to this P1 state, the OS can further request a higher performance state, namely a P0 state. This P0 state may thus be an opportunistic state in which, when power and/or thermal budget is available, processor hardware can configure the processor or at least portions thereof to operate at a higher than guaranteed frequency. In many implementations a processor can include multiple so-called bin frequencies above a guaranteed maximum frequency, also referred to as a P1 frequency. As used herein, a “bin frequency” corresponds to a smallest multiple by which a domain frequency can be updated. In some embodiments this bin frequency can be an integer multiple of a bus clock frequency, although the scope of the present invention is not limited in this regard.
Referring now to FIG. 1, shown is a flow diagram of a high level method in accordance with one embodiment of the present invention. As shown in FIG. 1, method 100 can be used to perform dynamic control of frequency ranges for a core domain in accordance with an embodiment of the present invention. As one example, method 100 can be implemented at least in part by an entity of the non-core domain itself. For example, as discussed above assume a non-core domain includes a graphics engine for which a graphics driver executes on the core domain. As seen, method 100 may begin by determining if a non-core domain is operating at a frequency less than a requested frequency (diamond 110). The driver can make the determination by comparing a frequency requested by the driver with an allocated frequency, which may be allocated by a power controller such as a power control unit (PCU) of the processor.
If the operating frequency of the non-core domain is lower than the requested frequency, control passes to block 120, where a request can be sent to the power controller to reduce a core domain frequency. That is, responsive to this determination, the driver can send a request to cause the core domain to operate at a lower frequency. Thus in contrast to conventional systems, a non-OS, non-core domain entity can make a request to cause an OS-controlled core domain to operate at a lower frequency. Although the embodiment just discussed is with regard to graphics driver control of the operating frequency range, in other implementations other privileged level code, such as ring zero code can perform this request. Note that in some embodiments, there can be limitations on allowing the graphics driver (and more generally a non-core domain) to control operating frequency of the core domain. For example with respect to a graphics engine, the graphics driver may only be allowed to control the core domain frequency for certain workloads, such as a 3D workload or a full-screen mode operation.
As further seen in FIG. 1, responsive to receipt of this request, the core domain frequency can be reduced (block 130). For example, the PCU logic can cause an operating frequency of the core domain to be reduced, e.g., by a predetermined amount, which can correspond to one or more bin frequencies. In a particular implementation as will be discussed further below, the dynamic control of the core domain frequency can be by way of limiting at least one of a maximum turbo frequency and a maximum guaranteed frequency of the core domain. In this way, a dynamically reduced frequency range is available for the core domain. By such dynamic range reduction, greater thermal and/or power budget can be made available for the non-core domain. Although described at this high level in the embodiment of FIG. 1, understand the scope of the present invention is not limited in this regard. For example, the embodiment shown in FIG. 1 is an implementation in which a non-core domain can control operating frequency of the core domain. In many implementations, a vice versa operation, namely core domain control of a non-core domain operating frequency, can also be performed, at least for certain operating modes or workloads.
Different manners of effecting a request for reduced frequency of the core domain are possible. In one particular implementation, a non-core domain can have access to certain configuration registers, e.g., of a PCU, that can enable dynamic control of a frequency range at which a core domain can operate. Such dynamic control can thus act to limit the core domain's frequency lower than its configured frequency levels, e.g., as set by fuses and/or configuration information for the particular processor as set during manufacture. In the context of an ACPI implementation, this lowering of the guaranteed operating frequency can thus violate the P1 guaranteed frequency at which the core domain is guaranteed to run.
Referring now to FIG. 2, shown is a flow diagram of a method for dynamic frequency range control of a core domain in accordance with an embodiment of the present invention. As shown in FIG. 2, method 200 may be performed by PCU logic, as well as software, firmware and/or logic of a non-core domain. Assume again for purposes of example that the non-core domain is a graphics engine on which a graphics workload is performed and that this graphics domain is controlled, at least in part, by a graphics driver. As seen, method 200 may iterate through a number of operations at a periodic interval (which is completed and begins a new iteration at block 210). In some embodiments this interval can be on the order of a number of milliseconds (ms), e.g., between approximately 10 and 100 ms. At diamond 220 it can be determined whether the non-core domain is receiving the operating frequency requested by its driver. If so, the iteration is concluded. Otherwise, control passes to diamond 230, where it can be determined whether this frequency limitation on the non-core domain originates from a package power limitation. Although the scope of the present invention is not limited this regard, this determination can be made by PCU logic, e.g., with reference to a power flag, which may be one of many flags of a performance monitor each to indicate whether a given subsystem can operate at a given performance state. For example, a PCU may include a performance monitor for subsystems including electrical, thermal, power, platform, and others. Based on an available performance level for each of these different subsystems, the PCU can determine a package performance state that corresponds to a minimum of these available performance levels. Thus if it is determined at diamond 230 that the frequency limit is due to another reason, dynamic frequency range control of the core domain cannot resolve the issue.
If the frequency limit is due to a package power limitation, control passes to block 240 where the non-core entity can determine the core domain frequency. In one embodiment, this determination can be made by reference to a current operating frequency register of the PCU that stores a current operating frequency. Then at diamond 250, it can be determined whether this core domain frequency is at or greater than a guaranteed frequency level. As discussed above, the guaranteed frequency level may correspond to a P1 frequency. In this way, the driver can determine whether the core domain is operating at least at its guaranteed frequency point of P1 . If not, control passes to block 260, where the driver can cause an update to a configuration register to cause the guaranteed frequency for the core domain to be reduced. As one example, a single configuration register may include multiple fields that expose dynamic frequency range control to a driver for a non-core domain. In this example, a first field of such configuration register can be used to cause a reduction in a guaranteed operating frequency of the core domain. As a result of this update, the PCU logic can, e.g., during a next iteration of its power control firmware, cause a reduction in the guaranteed operating frequency for the core domain. Thus if the core domain is currently operating at the guaranteed operating frequency, this frequency reduction can occur in that next iteration. If not, the information in the field can be used by the PCU logic during subsequent requests by the core domain for entry into the guaranteed performance mode.
Referring still to FIG. 2, if instead at diamond 250 it is determined that the core domain frequency is at or greater than the guaranteed frequency, control passes to block 270. There, the driver can cause an update to a configuration register to cause the maximum turbo frequency for the core domain to be reduced. In the above example, another field of the configuration register can be used to cause a reduction in the maximum turbo frequency of the core domain. As a result of this update, the PCU logic can, e.g., during a next iteration of its power control firmware, cause a reduction in the maximum turbo frequency for the core domain. Thus if the core domain is currently operating above the guaranteed operating frequency, this frequency reduction can occur in that next iteration. If not, the information in the field can be used by the PCU logic during subsequent requests by the core domain for entry into a performance mode higher than the guaranteed performance mode. Note that according to method 200, independent control of an upper and lower frequency limit of the core domain can be controlled.
As a result of these operations, the core domain will likely consume less power and accordingly a greater amount of a package power budget can be allocated to the non-core domain. Understand that although shown with only two domains in the embodiment of FIG. 2, additional domains are possible in a given system and in such embodiments, multiple domains can seek to control a dynamic frequency range of a core domain. And furthermore, in the case of multiple core domains such as where each core domain includes one or more cores, these multiple domains can independently request reductions in a frequency range of the other domains. Further, instead of a single multi-field configuration register, in another embodiment separate configuration registers may be present to expose control of maximum turbo frequency and guaranteed frequency to a non-core domain.
Referring now to Table 1, shown is an example of a configuration register, which may be present within a PCU, to enable non-core domain control of a core domain operating frequency.









TABLE 1







[31:16]
[15:8]
[7:0]


Reserved
PST_OFFSET
PST_LIM









Table 1 is thus for a single configuration register example including multiple fields, one of which to enable control of maximum turbo frequency and a second field to enable control of guaranteed frequency. Specifically in the embodiment of Table 1, the PST_OFFSET field provides, e.g., a graphics driver, a means of lowering the fused P1 frequency of the core domain. Assuming a bus clock (BCLK) frequency of 100 megahertz (MHz), an entry of 3 in the PST_OFFSET field corresponds to a request to lower the core domain guaranteed frequency by 3×100=300 MHz. In turn, a second field, namely PST_LIM, provides a means of capping the highest frequency at which the core domain can execute. Again assuming a BCLK frequency of 100 MHz, an entry of 20 in the PST_LIM field corresponds to a request to lower the maximum turbo frequency to 20×100=2000 MHz. Note that this implementation of Table 1 thus provides a ratioed value corresponding to the bus clock frequency. Instead in other embodiments rather than a ratio amount, a fixed value control can be provided, such that the values written to the fields of the configuration register can correspond to the maximum and minimum of the frequency range, respectively.
The configuration register example of Table 1 can be used in connection with the methods described herein such that at run time, if the graphics driver detects a case where the graphics engine is not able to operate at its maximum turbo frequency, it can issue a request to the PCU to update the configuration register or registers accordingly to lower the frequency range at which the core domain is allowed to run. In this way, the driver can dynamically update a frequency range for the core domain such that additional power headroom for the graphics domain can be obtained.
Referring now to FIG. 3, shown is a graphical illustration of dynamic frequency range control in accordance with an embodiment of the present invention. As shown in FIG. 3, for the example processor shown, a fused P1 frequency for the core domain is 2300 MHz, and its fused maximum turbo frequency is 3200 MHz. As an example, the frequency range between the P1 frequency of 2300 MHz and the 3200 MHz maximum frequency can be entered in a P0 performance state. Assume that during run time, the graphics driver determines that the guaranteed frequency of 2300 MHz causes the core domain to consume too much of the processor's power budget thereby leaving an insufficient amount of power headroom for the graphics domain to operate at its maximum turbo frequency. Under this scenario the graphics domain, e.g. via its driver, can use an interface to the PCU to update the configuration register of Table 1 to dynamically alter the allowed frequency range of operation for the core domain. As one example, a graphics driver can program a value of 5 to the PST_OFFSET field and a value of 28 to the PST_LIM field. This translates to dropping the core domain's guaranteed frequency from 2300 MHz to 2300−500=1800 MHz, and dropping the core domain's maximum turbo frequency from 3200 MHz to 2800 MHz. Under a power constrained scenario, the core domain can now legally drop down to 1800 MHz, thereby allowing the graphics domain more power headroom than if the core domain ran at its fused guaranteed frequency of 2300 MHz.
Referring now to FIG. 4, shown is a block diagram of a processor in accordance with an embodiment of the present invention. As shown in FIG. 4, processor 300 may be a multicore processor including a plurality of cores 310a-310n. In one embodiment, each such core may be of an independent power domain and can be configured to operate at an independent voltage and/or frequency, and to enter a turbo frequency mode when available headroom exists. The various cores may be coupled via an interconnect 315 to a system agent or uncore 320 that includes various components. As seen, the uncore 320 may include a shared cache 330 which may be a last level cache. In addition, the uncore may include an integrated memory controller 340, various interfaces 350 and a power control unit 355.
In various embodiments, power control unit 355 may include a frequency control logic 359, which may be a logic to control frequency of different domains of the processor. In the embodiment of FIG. 4, assuming that each core is of an independent power domain, logic 359 can dynamically control a range of frequencies at which each domain can operate. And, as described herein this control can be caused by another of the domains. As further seen in FIG. 4 to enable such cross-domain control of frequency range, different domains can access, e.g., via a register interface, a frequency range configuration storage 357. Although shown at this location in the embodiment of FIG. 4, understand that the scope of the present invention is not limited in this regard and the storage of this information can be in other locations, such as non-volatile storage or the like. Note that in an embodiment, each domain can access one or more configuration registers in this storage each associated with a given domain. As discussed above, these configuration registers can store maximum and guaranteed frequency values for a domain.
With further reference to FIG. 4, processor 300 may communicate with a system memory 360, e.g., via a memory bus. In addition, by interfaces 350, connection can be made to various off-chip components such as peripheral devices, mass storage and so forth. While shown with this particular implementation in the embodiment of FIG. 4, the scope of the present invention is not limited in this regard.
Referring now to FIG. 5, shown is a block diagram of a multi-domain processor in accordance with another embodiment of the present invention of the present invention. As shown in the embodiment of FIG. 5, processor 400 includes multiple domains. Specifically, a core domain 410 can include a plurality of cores 4100-410n, a graphics domain 420 can include one or more graphics engines, and a system agent domain 450 may further be present. In various embodiments, system agent domain 450 may execute at a fixed frequency and may remain powered on at all times to handle power control events and power management such that domains 410 and 420 can be controlled to dynamically change frequency, e.g., based on a power budget. Each of domains 410 and 420 may operate at different voltage and/or power. Note that while only shown with three domains, understand the scope of the present invention is not limited in this regard and additional domains can be present in other embodiments. For example, multiple core domains may be present each including at least one core.
In general, each core 410 may further include low level caches in addition to various execution units and additional processing elements. In turn, the various cores may be coupled to each other and to a shared cache memory formed of a plurality of units of a last level cache (LLC) 4400-440n. In various embodiments, LLC 440 may be shared amongst the cores and the graphics engine, as well as various media processing circuitry. As seen, a ring interconnect 430 thus couples the cores together, and provides interconnection between the cores, graphics domain 420 and system agent circuitry 450.
In the embodiment of FIG. 5, system agent domain 450 may include display controller 452 which may provide control of and an interface to an associated display. As further seen, system agent domain 450 may include a power control unit 455 which can include a frequency control logic 459 in accordance with an embodiment of the present invention. In various embodiments, this logic may execute algorithms such as shown in FIGS. 1-2 to thus dynamically control a frequency range of one domain responsive to a request from the other domain.
As further seen in FIG. 5, processor 400 can further include an integrated memory controller (IMC) 470 that can provide for an interface to a system memory, such as a dynamic random access memory (DRAM). Multiple interfaces 4800-480n may be present to enable interconnection between the processor and other circuitry. For example, in one embodiment at least one direct media interface (DMI) interface may be provided as well as one or more Peripheral Component Interconnect Express (PCI ExpressTM (PCIeTM)) interfaces. Still further, to provide for communications between other agents such as additional processors or other circuitry, one or more interfaces in accordance with a Intel® Quick Path Interconnect (QPI) protocol may also be provided. Although shown at this high level in the embodiment of FIG. 5, understand the scope of the present invention is not limited in this regard.
Embodiments may be implemented in many different system types. Referring now to FIG. 6, shown is a block diagram of a system in accordance with an embodiment of the present invention. As shown in FIG. 6, multiprocessor system 500 is a point-to-point interconnect system, and includes a first processor 570 and a second processor 580 coupled via a point-to-point interconnect 550. As shown in FIG. 6, each of processors 570 and 580 may be multicore processors, including first and second processor cores (i.e., processor cores 574a and 574b and processor cores 584a and 584b), although potentially many more cores may be present in the processors. Each of the processors can include a PCU or other logic to perform dynamic frequency range control of a domain of the processor responsive to a request of another domain, as described herein.
Still referring to FIG. 6, first processor 570 further includes a memory controller hub (MCH) 572 and point-to-point (P-P) interfaces 576 and 578. Similarly, second processor 580 includes a MCH 582 and P-P interfaces 586 and 588. As shown in FIG. 6, MCH's 572 and 582 couple the processors to respective memories, namely a memory 532 and a memory 534, which may be portions of system memory (e.g., DRAM) locally attached to the respective processors. First processor 570 and second processor 580 may be coupled to a chipset 590 via P-P interconnects 552 and 554, respectively. As shown in FIG. 6, chipset 590 includes P-P interfaces 594 and 598.
Furthermore, chipset 590 includes an interface 592 to couple chipset 590 with a high performance graphics engine 538, by a P-P interconnect 539. In turn, chipset 590 may be coupled to a first bus 516 via an interface 596. As shown in FIG. 6, various input/output (I/O) devices 514 may be coupled to first bus 516, along with a bus bridge 518 which couples first bus 516 to a second bus 520. Various devices may be coupled to second bus 520 including, for example, a keyboard/mouse 522, communication devices 526 and a data storage unit 528 such as a disk drive or other mass storage device which may include code 530, in one embodiment. Further, an audio I/O 524 may be coupled to second bus 520. Embodiments can be incorporated into other types of systems including mobile devices such as a smartphone, tablet computer, netbook, or so forth.
Embodiments may be implemented in code and may be stored on a non-transitory storage medium having stored thereon instructions which can be used to program a system to perform the instructions. The storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, solid state drives (SSDs), compact disk read-only memories (CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.
While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.

## Claims

1. A method comprising:
determining that a non-core domain of a multi-domain processor is not operating at a frequency requested by the non-core domain, the non-core domain including at least one graphics engine;
responsive to the determination, sending a request from the non-core domain to a power controller of the multi-domain processor to reduce a frequency of a core domain of the multi-domain processor, the core domain including at least one core; and
responsive to the request, reducing the frequency of the core domain.

2. The method of claim 1, further comprising updating a first field of a configuration register to cause the power controller to reduce a maximum turbo frequency of the core domain.

3. The method of claim 1, wherein reducing the core domain frequency includes causing a maximum turbo frequency of the core domain to be lowered from a fused value to a second turbo value less than the fused value.

4. The method of claim 2, further comprising updating a second field of the configuration register to cause the power controller to reduce a guaranteed frequency of the core domain.

5. The method of claim 3, further comprising determining whether the core domain is operating at least at a guaranteed frequency.

6. The method of claim 5, further comprising causing the guaranteed frequency of the core domain to be lowered from a second fused value to a second guaranteed value less than the second fused value.

7. A processor comprising:
a core domain having one or more cores, at least one non-core domain having at least one graphics engine, and a power controller, the core domain to operate at a frequency range between a maximum frequency and a guaranteed frequency, the maximum frequency and the guaranteed frequency set at manufacture, wherein the non-core domain is to cause the power controller to dynamically reduce at least one of the maximum frequency and the guaranteed frequency of the core domain.

8. The processor of claim 7, wherein the non-core domain is to update a first field of a configuration register if the non-core domain is operating at a frequency less than a requested frequency.

9. The processor of claim 7, wherein a driver of the non-core domain is to cause the power controller to dynamically reduce the at least one frequency, wherein the driver is to execute on the core domain.

10. The processor of claim 8, wherein the power controller is to limit the maximum frequency based on the updated first field of the configuration register.

11. The processor of claim 8, wherein the non-core domain is to thereafter update a second field of the configuration register.

12. The processor of claim 11, wherein the power controller is to limit the guaranteed frequency based on the updated second field of the configuration register.

13. The processor of claim 8, wherein the configuration register is located in the power controller, and is accessible to the non-core domain.

14. The processor of claim 8, wherein a driver of the non-core domain is to access the configuration register, wherein the driver is to execute on the core domain.

15. A system comprising:
a multi-domain processor including a core domain, at least one non-core domain, and a power controller, the core domain to operate at a frequency range between a maximum frequency and a guaranteed frequency, the maximum frequency and the guaranteed frequency set at manufacture, wherein the power controller includes a configuration register accessible to the non-core domain, the configuration register to store at least one value to be written by a driver of the non-core domain to enable a dynamic reduction in a frequency range at which the core domain can operate; and
a dynamic random access memory (DRAM) coupled to the multi-domain processor.

16. The system of claim 15, wherein the driver of the non-core domain is allowed to write to the configuration register when a first non-core domain workload is executing, and is prevented from writing to the configuration register when a second non-core domain workload is executing.

17. The system of claim 15, wherein the power controller includes a second configuration register accessible to the core domain, the second configuration register to store at least one value to be written by the core domain to enable a dynamic reduction in a frequency range at which the non-core domain can operate.

18. The system of claim 15, wherein the non-core domain is to operate at a higher frequency after the dynamic reduction in the core domain frequency range.

19. The system of claim 15, wherein the power controller is to first reduce the maximum frequency of the core domain, and to thereafter reduce the guaranteed frequency of the core domain only if the non-core domain is not operating at a requested frequency after the maximum frequency reduction.

20. The system of claim 15, wherein the driver of the non-core domain is to request the power controller to update the configuration register responsive to determining that the non-core domain is not operating at a frequency requested by the driver.

21. The system of claim 20, wherein responsive to the configuration register update, the power controller is to cause the core domain to operate at a frequency less than the guaranteed frequency set at manufacture, wherein the frequency less than the guaranteed frequency violates an operating system guaranteed frequency.