<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://gentoo-zh.org/extern.php?action=feed&amp;tid=9&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Gentoo中文社区 / Power management and ACPI options]]></title>
		<link>http://www.gentoo-zh.org/viewtopic.php?id=9</link>
		<description><![CDATA[Power management and ACPI options 最近发表的帖子。]]></description>
		<lastBuildDate>Wed, 03 Aug 2022 14:31:56 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Power management and ACPI options]]></title>
			<link>http://www.gentoo-zh.org/viewtopic.php?pid=9#p9</link>
			<description><![CDATA[<p>Power management and ACPI options<br />电源管理和ACPI选项</p><p>Suspend to RAM and standby<br />CONFIG_SUSPEND<br />&#160; &#160; &quot;休眠到内存&quot;(ACPI S3)支持.也就是系统休眠后,除了内存之外,其他所有部件都停止工作,重开机之后可以直接从内存中恢复运行状态.要使用此功能,你需要执行&quot;echo mem &gt; /sys/power/state&quot;命令,还需要在BIOS中开启S3支持,否则可能会有问题.</p><p>Skip kernel&#039;s sys_sync() on suspend to RAM/standby<br />&#160; &#160; &#160;跳过内核的sys_sync（）挂起到RAM /待机状态</p><p>&#160; &#160; Enable freezer for suspend to RAM/standby<br />&#160; &#160; CONFIG_SUSPEND_FREEZER<br />&#160; &#160; &#160; &#160; 选&quot;Y&quot;.除非你知道自己在做什么</p><p>Hibernation (aka &#039;suspend to disk&#039;)<br />CONFIG_HIBERNATION<br />&#160; &#160; &quot;休眠到硬盘&quot;(ACPI S4)支持.也就是将内存的内容保存到硬盘(hibernation),所有部件全都停止工作.<br />&#160; &#160; 要使用此功能,你首先需要使用内核引导参数&quot;resume=/dev/swappartition&quot;,<br />&#160; &#160; 然后执行&quot;echo disk &gt; /sys/power/state&quot;命令.如果你不想从先前的休眠状态中恢复,<br />&#160; &#160; 那么可以使用&quot;noresume&quot;内核引导参数.更多信息,可以参考&quot;Documentation/power/swsusp.txt&quot;文件.<br />&#160; &#160;<br />Default resume partition<br />CONFIG_PM_STD_PARTITION<br />&#160; &#160; 默认的休眠分区.这个分区必须是swap分区.不过这里设置的值会被明确的内核引导参数中的值覆盖.<br />&#160; &#160;<br />Opportunistic sleep<br />CONFIG_PM_AUTOSLEEP<br />&#160; &#160; 这是一种从安卓借鉴过来的休眠方式.这个特性在安卓系统上被称为&quot;suspend blockers&quot;或&quot;wakelocks&quot;.<br />&#160; &#160; 这是一种更激进的电源管理模式,以尽可能节约电力为目的.<br />&#160; &#160; 系统默认就处于休眠状态,仅为内存和少数唤醒系统所必须的设备供电,<br />&#160; &#160; 当有任务(唤醒源)需要运行的时候才唤醒相关组件工作,工作完成后又立即进入休眠状态.<br />&#160; &#160; 不过这些特性需要相应的设备驱动程序的支持.目前除了安卓设备,在PC和服务器领域,<br />&#160; &#160; 能够利用此特性的驱动还比较少,不过这是一项非常有前途的电源技术,喜欢尝鲜的可以考虑开启.<br />&#160; &#160;<br />User space wakeup sources interface<br />CONFIG_PM_WAKELOCKS<br />&#160; &#160; 允许用户空间的程序通过sys文件系统接口,创建/激活/撤销系统的&quot;唤醒源&quot;.需要与CONFIG_PM_AUTOSLEEP配合使用.</p><p>&#160; &#160; Maximum number of user space wakeup sources (0 = no limit)<br />&#160; &#160; CONFIG_PM_WAKELOCKS_LIMIT<br />&#160; &#160; &#160; &#160; 用户空间程序允许使用的&quot;唤醒源&quot;数量,&quot;0&quot;表示无限,最大值是&quot;100000&quot;.<br />&#160; &#160; Garbage collector for user space wakeup sources<br />&#160; &#160; CONFIG_PM_WAKELOCKS_GC<br />&#160; &#160; &#160; &#160; 对&quot;唤醒源&quot;对象使用垃圾回收.主要用于调试目的和Android环境.</p><p>Run-time PM core functionality<br />CONFIG_PM_RUNTIME<br />&#160; &#160; 允许IO设备(比如硬盘/网卡/声卡)在系统运行时进入省电模式,<br />&#160; &#160; 并可在收到(硬件或驱动产生的)唤醒信号后恢复正常.<br />&#160; &#160; 此功能通常需要硬件的支持.建议在笔记本/嵌入式等需要节约电力的设备上选&quot;Y&quot;.<br />&#160; &#160;<br />Device power management core functionality<br />&#160; &#160; 设备电源管理核心功能<br />&#160; &#160;<br />Power Management Debug Support<br />CONFIG_PM_DEBUG<br />&#160; &#160; 仅供调试使用<br />&#160; &#160;<br />Enable workqueue power-efficient mode by default<br />&#160; &#160; 默认情况下启用工作队列节能模式<br />&#160; &#160;<br />ACPI (Advanced Configuration and Power Interface) Support<br />CONFIG_ACPI<br />&#160; &#160; 高级配置与电源接口(Advanced Configuration and Power Interface)包括了软件和硬件方面的规范,<br />&#160; &#160; 目前已被软硬件厂商广泛支持,并且取代了许多过去的配置与电源管理接口,<br />&#160; &#160; 包括 PnP BIOS (Plug-and-Play BIOS), MPS(CONFIG_X86_MPPARSE),<br />&#160; &#160; APM(Advanced Power Management) 等.总之,ACPI已经成为x86平台必不可少的组件,<br />&#160; &#160; 如果你没有特别的理由,务必选中此项.<br />&#160; &#160; AML debugger interface<br />&#160; &#160; &#160; &#160; AML调试器界面<br />&#160; &#160; Deprecated /proc/acpi files<br />&#160; &#160; CONFIG_ACPI_PROCFS<br />&#160; &#160; &#160; &#160; 过时的 /proc/acpi 接口支持,建议关闭.<br />&#160; &#160; Deprecated power /proc/acpi directories<br />&#160; &#160; CONFIG_ACPI_PROCFS_POWER<br />&#160; &#160; &#160; &#160; 过时的 /proc/acpi 接口支持,建议关闭.<br />&#160; &#160; Allow supported ACPI revision to be overridden<br />&#160; &#160; &#160; &#160; 允许覆盖支持的ACPI修订版<br />&#160; &#160; EC read/write access through /sys/kernel/debug/ec<br />&#160; &#160; CONFIG_ACPI_EC_DEBUGFS<br />&#160; &#160; &#160; &#160; 仅供调试使用.<br />&#160; &#160; Deprecated /proc/acpi/event support<br />&#160; &#160; CONFIG_ACPI_PROC_EVENT<br />&#160; &#160; &#160; &#160; 过时的 /proc/acpi/event 接口支持,建议关闭.<br />&#160; &#160; AC Adapter<br />&#160; &#160; CONFIG_ACPI_AC<br />&#160; &#160; &#160; &#160; 允许在外接交流电源和内置电池之间进行切换.<br />&#160; &#160; Battery<br />&#160; &#160; CONFIG_ACPI_BATTERY<br />&#160; &#160; &#160; &#160; 允许通过 /proc/acpi/battery 接口查看电池信息.<br />&#160; &#160; Button<br />&#160; &#160; CONFIG_ACPI_BUTTON<br />&#160; &#160; &#160; &#160; 允许守护进程通过 /proc/acpi/event 接口捕获power/sleep/lid(合上笔记本)按钮事件,<br />&#160; &#160; &#160; &#160; 并执行相应的动作,软关机(poweroff)也需要它的支持.<br />&#160; &#160; Video<br />&#160; &#160; CONFIG_ACPI_VIDEO<br />&#160; &#160; &#160; &#160; 对主板上的集成显卡提供ACPI支持.注意:仅支持集成显卡.<br />&#160; &#160; Fan<br />&#160; &#160; CONFIG_ACPI_FAN<br />&#160; &#160; &#160; &#160; 允许用户层的程序对风扇进行控制(开/关/查询状态)<br />&#160; &#160; Dock<br />&#160; &#160; CONFIG_ACPI_DOCK<br />&#160; &#160; &#160; &#160; 支持兼容ACPI规范的扩展坞(比如 IBM Ultrabay 和 Dell Module Bay)支持.<br />&#160; &#160; Processor<br />&#160; &#160; CONFIG_ACPI_PROCESSOR<br />&#160; &#160; &#160; &#160; 在支持 ACPI C2/C3 的CPU上,将ACPI安装为idle处理程序.<br />&#160; &#160; &#160; &#160; 有几种CPU频率调节驱动依赖于它.而且目前的CPU都已经支持ACPI规范,建议开启此项.<br />&#160; &#160; IPMI<br />&#160; &#160; CONFIG_ACPI_IPMI<br />&#160; &#160; &#160; &#160; 允许ACPI使用IPMI(智能平台管理接口)的请求/应答消息访问BMC(主板管理控制器).<br />&#160; &#160; &#160; &#160; IPMI通常出现在服务器中,以允许通过诸如ipmitool这样的工具监视服务器的<br />&#160; &#160; &#160; &#160; 物理健康特征(温度/电压/风扇状态/电源状态).<br />&#160; &#160; Processor Aggregator<br />&#160; &#160; CONFIG_ACPI_PROCESSOR_AGGREGATOR<br />&#160; &#160; &#160; &#160; 支持 ACPI 4.0 加入的处理器聚合器(processor Aggregator)功能,<br />&#160; &#160; &#160; &#160; 以允许操作系统对系统中所有的CPU进行统一的配置和控制.<br />&#160; &#160; &#160; &#160; 目前只支持逻辑处理器idling功能,其目标是降低耗电量.<br />&#160; &#160; Thermal Zone<br />&#160; &#160; CONFIG_ACPI_THERMAL<br />&#160; &#160; &#160; &#160; ACPI thermal zone 支持.系统温度过高时可以及时调整工作状态以避免你的CPU被烧毁.<br />&#160; &#160; &#160; &#160; 目前所有CPU都支持此特性.务必开启.参见CONFIG_THERMAL选项.&#160; &#160; &#160;<br />&#160; &#160; Allow upgrading ACPI tables via initrd<br />&#160; &#160; &#160; &#160; 允许通过initrd升级ACPI表<br />&#160; &#160; NUMA support<br />&#160; &#160; CONFIG_ACPI_NUMA<br />&#160; &#160; &#160; &#160; 通过读取系统固件中的ACPI表,获得NUMA系统的CPU及物理内存分布信息.NUMA系统必选.<br />&#160; &#160; Custom DSDT Table file to include<br />&#160; &#160; CONFIG_ACPI_CUSTOM_DSDT_FILE<br />&#160; &#160; &#160; &#160; 允许将一个定制过的DSDT编译进内核.<br />&#160; &#160; &#160; &#160; 详情参见&quot;Documentation/acpi/dsdt-override.txt&quot;文档.看不懂的请保持空白.<br />&#160; &#160; ACPI tables override via initrd<br />&#160; &#160; CONFIG_ACPI_INITRD_TABLE_OVERRIDE<br />&#160; &#160; &#160; &#160; 允许initrd更改 ACPI tables 中的任意内容. ACPI tables 是BIOS提供给OS的硬件配置数据,<br />&#160; &#160; &#160; &#160; 包括系统硬件的电源管理和配置管理.详情参见&quot;Documentation/acpi/initrd_table_override.txt&quot;文件.<br />&#160; &#160; Debug Statements<br />&#160; &#160; CONFIG_ACPI_DEBUG<br />&#160; &#160; &#160; &#160; 详细的ACPI调试信息,不搞开发就别选.<br />&#160; &#160; PCI slot detection driver<br />&#160; &#160; CONFIG_ACPI_PCI_SLOT<br />&#160; &#160; &#160; &#160; 将每个PCI插槽都作为一个单独的条目列在 /sys/bus/pci/slots/ 目录中,<br />&#160; &#160; &#160; &#160; 有助于将设备的物理插槽位置与逻辑的PCI总线地址进行对应.不确定的选&quot;No&quot;.<br />&#160; &#160; Power Management Timer Support<br />&#160; &#160; CONFIG_X86_PM_TIMER<br />&#160; &#160; &#160; &#160; ACPI PM Timer,简称&quot;ACPI Timer&quot;,是一种集成在主板上的硬件时钟发生器,提供3.579545MHz固定频率.<br />&#160; &#160; &#160; &#160; 这是比较传统的硬件时钟发生器(HPET则是比较新型的硬件时钟发生器),<br />&#160; &#160; &#160; &#160; 目前所有的主板都支持,而且是ACPI规范不可分割的部分.除非你确定不需要,否则必选.<br />&#160; &#160; Container and Module Devices<br />&#160; &#160; CONFIG_ACPI_CONTAINER<br />&#160; &#160; &#160; &#160; 支持 NUMA节点/CPU/内存 的热插拔. Device ID: ACPI0004, PNP0A05, PNP0A06<br />&#160; &#160; Memory Hotplug<br />&#160; &#160; CONFIG_ACPI_HOTPLUG_MEMORY<br />&#160; &#160; &#160; &#160; 内存热插拔支持. Device ID: PNP0C80<br />&#160; &#160; Smart Battery System<br />&#160; &#160; CONFIG_ACPI_SBS<br />&#160; &#160; &#160; &#160; 智能电池系统(Smart Battery System)可以让笔记型电脑显示及管理详细精确的电池状态信息.<br />&#160; &#160; &#160; &#160; 使用锂电池的笔记本电脑必备利器.但遗憾的是并不是所有笔记本都支持这项特性.<br />&#160; &#160; Hardware Error Device<br />&#160; &#160; CONFIG_ACPI_HED<br />&#160; &#160; &#160; &#160; Hardware Error Device (Device ID: PNP0C33) 能够通过 SCI 报告一些硬件错误(通常是已经被纠正的错误).<br />&#160; &#160; &#160; &#160; 如果你的系统中有设备ID为&quot;PNP0C33&quot;的设备(比如某些Intel芯片组),那么就选上.<br />&#160; &#160; Allow ACPI methods to be inserted/replaced at run time<br />&#160; &#160; CONFIG_ACPI_CUSTOM_METHOD<br />&#160; &#160; &#160; &#160; 允许在不断电的情况下直接对ACPI的功能进行删改,<br />&#160; &#160; &#160; &#160; 包含一定危险性,它允许root任意修改内存中内核空间的内容.仅用于调试.<br />&#160; &#160; Boottime Graphics Resource Table support<br />&#160; &#160; CONFIG_ACPI_BGRT<br />&#160; &#160; &#160; &#160; 在 /sys/firmware/acpi/bgrt/ 中显示<br />&#160; &#160; &#160; &#160; ACPI Boottime Graphics Resource Table ,以允许操作系统获取固件中的启动画面(splash).<br />&#160; &#160; Hardware-reduced ACPI support only<br />&#160; &#160; ACPI NVDIMM Firmware Interface Table (NFIT)<br />&#160; &#160; &#160; &#160; ACPI NVDIMM固件接口表（NFIT）<br />&#160; &#160; ACPI Platform Error Interface (APEI)<br />&#160; &#160; CONFIG_ACPI_APEI<br />&#160; &#160; &#160; &#160; 高级平台错误接口(ACPI Platform Error Interface)是RAS(Reliability,<br />&#160; &#160; &#160; &#160; Availability and Serviceability)的一部分,是定义在 ACPI 4.0 规范中的一个面向硬件错误管理的接口,<br />&#160; &#160; &#160; &#160; 主要是为了统一 firmware/BIOS 和 OS 之间的错误交互机制,使用标准的错误接口进行管理,<br />&#160; &#160; &#160; &#160; 同时也扩展了错误接口的内容以便实现更加灵活丰富的功能.<br />&#160; &#160; &#160; &#160; APEI Generic Hardware Error Source<br />&#160; &#160; &#160; &#160; CONFIG_ACPI_APEI_GHES<br />&#160; &#160; &#160; &#160; &#160; &#160; &quot;Firmware First Mode&quot;支持.由于BIOS/FIRMWARE是平台相关的,<br />&#160; &#160; &#160; &#160; &#160; &#160; 因此BIOS/FIRMWARE比OS更清楚硬件平台的配置情况,<br />&#160; &#160; &#160; &#160; &#160; &#160; 甚至包含各种必须的修正/定制/优化.这样,在&quot;Firmware First&quot;模式下,<br />&#160; &#160; &#160; &#160; &#160; &#160; BIOS/FIRMWARE利用这一优势,可以有针对性的对发生的硬件错误进行分析/处理/分发,<br />&#160; &#160; &#160; &#160; &#160; &#160; 也可以更准确的记录错误的现场信息.这样,不但对硬件错误可以做出更准确,更复杂的处理,<br />&#160; &#160; &#160; &#160; &#160; &#160; 而且可以降低OS的复杂性和冗余度.建议开启.<br />&#160; &#160; &#160; &#160; APEI PCIe AER logging/recovering support<br />&#160; &#160; &#160; &#160; CONFIG_ACPI_APEI_PCIEAER<br />&#160; &#160; &#160; &#160; &#160; &#160; 让 PCIe AER errors 首先通过 APEI firmware 进行报告.<br />&#160; &#160; APEI memory error recovering support<br />&#160; &#160; CONFIG_ACPI_APEI_MEMORY_FAILURE<br />&#160; &#160; &#160; &#160; 让 Memory errors 首先通过 APEI firmware 进行报告.<br />&#160; &#160; APEI Error INJection (EINJ)<br />&#160; &#160; CONFIG_ACPI_APEI_EINJ<br />&#160; &#160; &#160; &#160; 仅供调试使用.<br />&#160; &#160; APEI Error Record Serialization Table (ERST) Debug Support<br />&#160; &#160; CONFIG_ACPI_APEI_ERST_DEBUG<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; DPTF Platform Power Participant<br />&#160; &#160; &#160; &#160; DPTF平台电力参与者<br />&#160; &#160; Extended Error Log support<br />&#160; &#160; &#160; &#160; 扩展错误日志支持<br />&#160; &#160; PMIC (Power Management Integrated Circuit) operation region support<br />&#160; &#160; &#160; &#160; PMIC(电源管理集成电路)操作区域支持<br />&#160; &#160; ACPI configfs support<br />&#160; &#160; &#160; &#160; ACPI configfs支持</p><p>SFI (Simple Firmware Interface) Support<br />CONFIG_SFI<br />&#160; &#160; 简单固件接口规范(Simple Firmware Interface)使用一种轻量级的简单方法(通过内存中的一张静态表格)<br />&#160; &#160; 从firmware向操作系统传递信息.目前这个规范仅用于第二代 Intel Atom 平台,其核心名称是&quot;Moorestown&quot;.</p><p>CPU Frequency scaling<br />CONFIG_CPU_FREQ<br />&#160; &#160; CPUfreq子系统允许动态改变CPU主频,达到省电和降温的目的.<br />&#160; &#160; 现如今的CPU都已经支持动态频率调整,建议开启.不过,如果你是为虚拟机编译内核,<br />&#160; &#160; 就没有必要开启了,由宿主机内核去控制就OK了.<br />&#160; &#160; CPU frequency translation statistics<br />&#160; &#160; CONFIG_CPU_FREQ_STAT<br />&#160; &#160; &#160; &#160; 通过sysfs文件系统输出CPU频率变化的统计信息<br />&#160; &#160; &#160; &#160; CPU frequency translation statistics details<br />&#160; &#160; &#160; &#160; CONFIG_CPU_FREQ_STAT_DETAILS<br />&#160; &#160; &#160; &#160; &#160; &#160; 输出更详细的CPU频率变化统计信息<br />&#160; &#160; Default CPUFreq governor<br />&#160; &#160; &#160; &#160; 默认的CPU频率调节策略.不同策略拥有不同的调节效果.<br />&#160; &#160; &#039;performance&#039; governor<br />&#160; &#160; CONFIG_CPU_FREQ_GOV_PERFORMANCE<br />&#160; &#160; &#160; &#160; &#039;性能&#039;优先,静态的将频率设置为cpu支持的最高频率<br />&#160; &#160; &#039;powersave&#039; governor<br />&#160; &#160; &#160; CONFIG_CPU_FREQ_GOV_POWERSAVE<br />&#160; &#160; &#160; &#160; &#039;节能&#039;优先,静态的将频率设置为cpu支持的最低频率<br />&#160; &#160; &#039;userspace&#039; governor for userspace frequency scaling<br />&#160; &#160; &#160; CONFIG_CPU_FREQ_GOV_USERSPACE<br />&#160; &#160; &#160; &#160; 既允许手动调整cpu频率,也允许用户空间的程序动态的调整cpu频率(需要额外的调频软件)<br />&#160; &#160; &#039;ondemand&#039; cpufreq policy governor<br />&#160; &#160; &#160; CONFIG_CPU_FREQ_GOV_ONDEMAND<br />&#160; &#160; &#160; &#160; &#039;立即响应&#039;,周期性的考察CPU负载并自动的动态调整cpu频率(不需要额外的调频软件),适合台式机<br />&#160; &#160; &#039;conservative&#039; cpufreq governor<br />&#160; &#160; &#160; CONFIG_CPU_FREQ_GOV_CONSERVATIVE<br />&#160; &#160; &#160; &#160; &#039;保守&#039;,和&#039;ondemand&#039;相似,但是频率的升降是渐变式的(幅度不会很大),更适合用于笔记本/PDA/x86_64环境<br />&#160; &#160; &#160;x86 CPU frequency scaling drivers<br />&#160; &#160; &#160; &#160; CPU频率调节器驱动<br />&#160; &#160; intel P state control<br />&#160; &#160; &#160; &#160; CONFIG_X86_INTEL_PSTATE<br />&#160; &#160; &#160; &#160; &#160; &#160;Intel CPU 的 P-state 驱动,面向&quot;Sandy Bridge&quot;/&quot;Ivy Bridge&quot;/&quot;Haswell&quot;或更新的CPU微架构,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以更好的支持&quot;Turbo Boost 2.0&quot;技术.<br />&#160; &#160; Processor Clocking Control interface driver<br />&#160; &#160; &#160; &#160; CONFIG_X86_PCC_CPUFREQ<br />&#160; &#160; &#160; &#160; &#160; &#160; PCC(Processor Clocking Control)接口支持.此种接口仅对某些HP Proliant系列服务器有意义.<br />&#160; &#160; &#160; &#160; &#160; &#160; 更多细节可以参考&quot;Documentation/cpu-freq/pcc-cpufreq.txt&quot;文件.<br />&#160; &#160; ACPI Processor P-States driver<br />&#160; &#160; &#160; &#160; CONFIG_X86_ACPI_CPUFREQ<br />&#160; &#160; &#160; &#160; &#160; &#160; 这是首选的驱动(CONFIG_X86_INTEL_PSTATE也依赖于它),<br />&#160; &#160; &#160; &#160; &#160; &#160; 同时支持Intel和AMD的CPU.除非你的CPU实在太老,否则必选.<br />&#160; &#160; &#160; &#160; Legacy cpb sysfs knob support for AMD CPUs<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160;C ONFIG_X86_ACPI_CPUFREQ_CPB<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为了兼容旧的用户空间程序而设置,建议关闭.<br />&#160; &#160; AMD Opteron/Athlon64 PowerNow!<br />&#160; &#160; &#160; &#160; CONFIG_X86_POWERNOW_K8<br />&#160; &#160; &#160; &#160; &#160; &#160; 过时的驱动,仅为老旧的K8核心的AMD处理器提供支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; K10以及更新的CPU应该使用CONFIG_X86_ACPI_CPUFREQ驱动.<br />&#160; &#160; AMD frequency sensitivity feedback powersave bias<br />&#160; &#160; &#160; &#160; CONFIG_X86_AMD_FREQ_SENSITIVITY<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果你使用 AMD Family 16h 或者更高级别的处理器,同时又使用&quot;ondemand&quot;频率调节器,<br />&#160; &#160; &#160; &#160; &#160; &#160; 开启此项可以更有效的进行频率调节(在保证性能的前提下更节能).<br />&#160; &#160; Intel Enhanced SpeedStep (deprecated)<br />&#160; &#160; &#160; &#160; CONFIG_X86_SPEEDSTEP_CENTRINO<br />&#160; &#160; &#160; &#160; &#160; &#160; 已被时代抛弃的驱动,仅对老旧的迅驰平台 Intel Pentium M 或者 Intel Xeons 处理器有意义.<br />&#160; &#160; Intel Pentium 4 clock modulation<br />&#160; &#160; &#160; &#160; CONFIG_X86_P4_CLOCKMOD<br />&#160; &#160; &#160; &#160; &#160; &#160; 已被时代抛弃的驱动,仅对支持老旧的Speedstep技术的<br />&#160; &#160; &#160; &#160; &#160; &#160; Intel Pentium 4 / XEON 处理器有意义.而且即便是在这样的CPU上,<br />&#160; &#160; &#160; &#160; &#160; &#160; 因为种种兼容性问题可能导致的不稳定,也不建议开启.</p><p>CPU idle PM support<br />&#160; &#160;CONFIG_CPU_IDLE<br />&#160; &#160; CPU idle 指令支持,该指令可以让CPU在空闲时&quot;打盹&quot;以节约电力和减少发热.<br />&#160; &#160; 只要是支持ACPI的CPU就应该开启.由于所有64位CPU都已支持ACPI,所以不必犹豫,<br />&#160; &#160; 开启![提示]为虚拟机编译的内核就没有必要开启了,由宿主机内核去控制就OK了.<br />&#160; &#160; Support multiple cpuidle drivers<br />&#160; &#160; &#160; CONFIG_CPU_IDLE_MULTIPLE_DRIVERS<br />&#160; &#160; &#160; &#160; 允许CONFIG_CPU_IDLE为每个不同的CPU使用不同的驱动.<br />&#160; &#160; &#160; &#160; 仅在你的系统由多个不同型号的CPU组成,并且具有不同的唤醒潜伏时间和状态的时候才需要开启.<br />&#160; &#160; Ladder governor (for periodic timer tick)<br />&#160; &#160; &#160; &#160; 梯形调速器（用于定期计时器滴答）<br />&#160; &#160; Menu governor (for tickless system)<br />&#160; &#160; &#160; &#160; 菜单调控器（用于无滴答系统）<br />&#160; &#160; &#160; &#160;<br />Cpuidle Driver for Intel Processors<br />CONFIG_INTEL_IDLE<br />&#160; &#160; 专用于Intel CPU的cpuidle驱动.而CONFIG_CPU_IDLE则是用于非Intel的CPU.<br />Memory power savings<br />&#160; &#160; 内存节能<br />&#160; &#160; Intel chipset idle memory power saving driver<br />&#160; &#160; CONFIG_I7300_IDLE<br />&#160; &#160; &#160; &#160; 在某些具备内存节能特性的intel服务器芯片组上,让内存也可以在空闲时通过idle指令&quot;打盹&quot;.这些芯片组必须具备 I/O AT 支持(例如 Intel 7300).同时内存也需要支持此特性.</p>]]></description>
			<author><![CDATA[dummy@example.com (batsom)]]></author>
			<pubDate>Wed, 03 Aug 2022 14:31:56 +0000</pubDate>
			<guid>http://www.gentoo-zh.org/viewtopic.php?pid=9#p9</guid>
		</item>
	</channel>
</rss>
