/linux/Documentation/scheduler/ |
H A D | sched-energy.rst | 9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an 10 Energy Model (EM) of the CPUs to select an energy efficient CPU for each task, 20 because this is where the potential for saving energy through scheduling is 25 please refer to its documentation (see Documentation/power/energy-model.rst). 32 - energy = [joule] (resource like a battery on powered devices) 33 - power = energy/time = [joule/second] = [watt] 35 The goal of EAS is to minimize energy, while still getting the job done. That 44 energy [J] 50 scheduler. This alternative considers two objectives: energy-efficiency and 54 implications of its decisions rather than blindly applying energy-saving [all …]
|
H A D | index.rst | 18 sched-energy
|
/linux/Documentation/devicetree/bindings/net/ |
H A D | smsc-lan87xx.txt | 12 - smsc,disable-energy-detect: 13 If set, do not enable energy detect mode for the SMSC phy. 14 default: enable energy detect mode 17 smsc phy with disabled energy detect mode on an am335x based board. 25 smsc,disable-energy-detect;
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-firmware-papr-energy-scale-info | 5 energy/frequency on Linux running as a PAPR guest. 9 energy-savings mode and processor frequency. 19 Description: String description of the energy attribute of <id> 24 Description: Numeric value of the energy attribute of <id> 29 Description: String value of the energy attribute of <id>
|
H A D | sysfs-bus-iio-adc-pac1934 | 9 current, power and accumulated energy.
|
/linux/arch/x86/events/ |
H A D | rapl.c | 402 RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01"); 403 RAPL_EVENT_ATTR_STR(energy-pkg , rapl_pkg, "event=0x02"); 404 RAPL_EVENT_ATTR_STR(energy-ram , rapl_ram, "event=0x03"); 405 RAPL_EVENT_ATTR_STR(energy-gpu , rapl_gpu, "event=0x04"); 406 RAPL_EVENT_ATTR_STR(energy-psys, rapl_psys, "event=0x05"); 408 RAPL_EVENT_ATTR_STR(energy-cores.unit, rapl_cores_unit, "Joules"); 409 RAPL_EVENT_ATTR_STR(energy-pkg.unit , rapl_pkg_unit, "Joules"); 410 RAPL_EVENT_ATTR_STR(energy-ram.unit , rapl_ram_unit, "Joules"); 411 RAPL_EVENT_ATTR_STR(energy-gpu.unit , rapl_gpu_unit, "Joules"); 412 RAPL_EVENT_ATTR_STR(energy-psys.unit, rapl_psys_unit, "Joules"); [all …]
|
/linux/Documentation/devicetree/bindings/hwmon/ |
H A D | vexpress.txt | 10 "arm,vexpress-energy" 19 energy@0 { 20 compatible = "arm,vexpress-energy";
|
/linux/Documentation/hwmon/ |
H A D | ltc2947.rst | 21 The LTC2947 is a high precision power and energy monitor that measures current, 22 voltage, power, temperature, charge and energy. The device supports both SPI 24 The device also measures accumulated quantities as energy. It has two banks of 25 register's to read/set energy related values. These banks can be configured 97 energy1_input Measured energy over time (in microJoule) 99 energy2_input Measured energy over time (in microJoule)
|
H A D | ibmaem.rst | 26 This driver implements sensor reading support for the energy and power meters 31 The v1 AEM interface has a simple set of features to monitor energy use. There 32 is a register that displays an estimate of raw energy consumption since the 37 range of energy and power use registers, the power cap as set by the AEM
|
/linux/Documentation/translations/zh_CN/scheduler/ |
H A D | sched-energy.rst | 4 :Original: Documentation/scheduler/sched-energy.rst 30 它提供的内容,请参考其文档(见Documentation/power/energy-model.rst)。 77 见Documentation/power/energy-model.rst) 287 Documentation/power/energy-model.rst中的独立EM框架部分。
|
H A D | index.rst | 27 sched-energy
|
/linux/tools/testing/selftests/amd-pstate/ |
H A D | gitsource.sh | 91 …$PERF stat -a --per-socket -I 1000 -e power/energy-pkg/ /usr/bin/time -o $BACKUP_DIR/$OUTFILE_GIT.… 120 grep Joules $OUTFILE_GIT-perf-$1-$2.log | awk '{print $4}' > $OUTFILE_GIT-energy-$1-$2.log 121 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_GIT-energy-$1-$2.log) 175 …$OUTFILE_GIT.result | grep "power consumption(J):" | awk '{print $NF}' > $OUTFILE_GIT-energy-$1.log 176 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_GIT-energy-$1.log) 179 avg_en=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum/'$LOOP_TIMES'}' $OUTFILE_GIT-energy-$1.log)
|
H A D | tbench.sh | 71 …$PERF stat -a --per-socket -I 1000 -e power/energy-pkg/ tbench -t $TIME_LIMIT $PROCESS_NUM > $OUTF… 102 grep Joules $OUTFILE_TBENCH-perf-$1-$2.log | awk '{print $4}' > $OUTFILE_TBENCH-energy-$1-$2.log 103 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-energy-$1-$2.log) 157 …LE_TBENCH.result | grep "power consumption(J):" | awk '{print $NF}' > $OUTFILE_TBENCH-energy-$1.log 158 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-energy-$1.log) 161 …avg_en=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum/'$LOOP_TIMES'}' $OUTFILE_TBENCH-energy-$1.l…
|
/linux/drivers/powercap/ |
H A D | Kconfig | 84 bool "Add CPU power capping based on the energy model" 88 energy model. 91 bool "Add device power capping based on the energy model" 95 energy model.
|
H A D | intel_rapl_common.c | 302 static int get_max_energy_counter(struct powercap_zone *pcd_dev, u64 *energy) in get_max_energy_counter() argument 306 *energy = rapl_unit_xlate(rd, ENERGY_UNIT, ENERGY_STATUS_MASK, 0); in get_max_energy_counter() 1922 RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01"); 1923 RAPL_EVENT_ATTR_STR(energy-pkg, rapl_pkg, "event=0x02"); 1924 RAPL_EVENT_ATTR_STR(energy-ram, rapl_ram, "event=0x03"); 1925 RAPL_EVENT_ATTR_STR(energy-gpu, rapl_gpu, "event=0x04"); 1926 RAPL_EVENT_ATTR_STR(energy-psys, rapl_psys, "event=0x05"); 1928 RAPL_EVENT_ATTR_STR(energy-cores.unit, rapl_unit_cores, "Joules"); 1929 RAPL_EVENT_ATTR_STR(energy-pkg.unit, rapl_unit_pkg, "Joules"); 1930 RAPL_EVENT_ATTR_STR(energy-ram.unit, rapl_unit_ram, "Joules"); [all …]
|
/linux/Documentation/arch/x86/ |
H A D | intel-hfi.rst | 14 The HFI gives the operating system a performance and energy efficiency 22 about the performance and energy efficiency of each CPU in the system. Each 38 task placement decisions. For instance, if either the performance or energy 41 that processor for performance or energy efficiency reasons, respectively.
|
/linux/arch/arm/boot/dts/arm/ |
H A D | vexpress-v2p-ca15_a7.dts | 394 energy-a15 { 395 /* Total energy for the two A15 cores */ 396 compatible = "arm,vexpress-energy"; 401 energy-a7 { 402 /* Total energy for the three A7 cores */ 403 compatible = "arm,vexpress-energy";
|
H A D | vexpress-v2p-ca15-tc1.dts | 231 energy { 232 /* Total energy */ 233 compatible = "arm,vexpress-energy";
|
/linux/Documentation/translations/zh_CN/power/ |
H A D | energy-model.rst | 4 :Original: Documentation/power/energy-model.rst 28 Documentation/scheduler/sched-energy.rst。对于一些子系统,比如热能或
|
H A D | index.rst | 17 energy-model
|
/linux/drivers/gpu/drm/i915/ |
H A D | i915_hwmon.c | 136 hwm_energy(struct hwm_drvdata *ddat, long *energy) in hwm_energy() argument 161 *energy = mul_u64_u32_shr(ei->accum_energy, SF_ENERGY, in hwm_energy() 288 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT), 295 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT), 844 long energy; in hwm_get_preregistration_info() local 897 hwm_energy(ddat, &energy); in hwm_get_preregistration_info() 900 hwm_energy(&hwmon->ddat_gt[i], &energy); in hwm_get_preregistration_info()
|
/linux/drivers/gpu/drm/xe/ |
H A D | xe_hwmon.c | 260 xe_hwmon_energy_get(struct xe_hwmon *hwmon, int channel, long *energy) in xe_hwmon_energy_get() argument 276 *energy = mul_u64_u32_shr(ei->accum_energy, SF_ENERGY, in xe_hwmon_energy_get() 438 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT | HWMON_E_LABEL, HWMON_E_INPUT | HWMON_E_LABEL), 786 long energy; in xe_hwmon_get_preregistration_info() local 809 xe_hwmon_energy_get(hwmon, channel, &energy); in xe_hwmon_get_preregistration_info()
|
/linux/Documentation/power/powercap/ |
H A D | powercap.rst | 154 the zones and subzones contain energy monitoring attributes (energy_uj, 197 Current energy counter in micro joules. Write "0" to reset. 201 Range of the above energy counter in micro-joules. 212 It is possible that some domains have both power ranges and energy counter ranges;
|
/linux/Documentation/power/ |
H A D | index.rst | 14 energy-model
|
/linux/Documentation/admin-guide/pm/ |
H A D | amd-pstate.rst | 116 more energy efficient than higher performance levels. This register 159 toward performance (0x0) or energy efficiency (0xff). 281 to the low-level firmware about the user's desired energy vs efficiency 287 The current energy performance preference can be read from this attribute. 288 and user can change current preference according to energy or performance needs 326 platforms. The AMD P-States mechanism is the more performance and energy 338 and takes into account only the values set to the minimum, maximum and energy 354 wants to bias toward performance (0x0) or energy efficiency (0xff) to the CPPC firmware. 608 These changes include desire performance, frequency, load, performance, energy etc. 615 These changes include desire performance, frequency, load, time, energy etc. [all …]
|