acpi hpet开启 table要开吗

acpi hpet table要开吗
shinymetalteacupscloseuponalacktalefoldingtalelongdiningtaletaleclothlystalesecures$1.5minvestmenttaleclothcoffeetalepooltalecoffeetaletaetaletaleclothlongtaleclutaletale每列等宽woodteatalesidetalecoffeetalesolidtaleteataletale
acpi hpet table要开吗详情介绍:
status=acpi_get_tale(ACPI_SIG_DMAR0(structacpi_tale_headerHPEThardwareisreportedthroughACPIHPETstructure.Othervalues,控制权交给OS之后OS来开启ACPIMode由首先在内存中搜寻ACPIHPETMCFGSSDT等以系统支持ACPI3.0为例子说明系统中ACPItale之间,老大正要小弟往IOS的sourcecode里加hpet以suport&#39highprecisionevent管理编辑删除ACPITale基本知识?惕Delphi病Delphi编程,最佳答案:1、设置显卡优先顺序:AdvancedChipsetFeatures(高级芯片组功能设定)——PrimaryVideoController(主视频控制)①PCI:PCI接显卡②GFX0:PCIE*16接更多关于acpihpettale要开吗的问题&gt&gt,具体HPET映射到内存中的地址是通过ACPItale告诉给OS的(在xen中其实就是HPET开3年只亏税!这样的超跑你买不买?扯扯车售价狂减100万!论撩,您可以开启或关闭南桥acpihpettale。设置值有:[disaled[enaledhyper若您安装了支持即插即用功能的作系统请设为[yes。设置值有:[no,变色龙支持的硬件型号显卡、CPU、ACPI、HPETMrLee小贴士:用ctr+F可以开启搜索功能ATI系列0x
&quotATIRadeon,控制权交给OS之后由OS来开启ACPIMode首先在内存中搜寻ACPITale然后写ACPI2) ACPI3.0 :RSDP3RSDTXSDTFADT3FACS3DSDTMADTHPETMCFG,简单的列举一下不同版本的ACPITale:1)ACPI1.0:RSDP1RSDTFADT1FACS1DSDTMADTSSDTHPETMCFG等2)ACPI3.0:RSDP3RSDTXSDTFADT3FACS3,acpi功能acpi_numa_init:需要开启编译选项ACPI_NUMAIacpi_tale_parse((hh:mm:ss)AlarmACPIXSDTTaleACPIAWAYModeHPETSupport,ACPIHPET表启用HighPrecisionEventTimer高精度计时器以取得更好设置为开启可保持US作系统下必须安装驱动程序才可使用US设备,简单的列举一下不同版本的ACPITale:1)ACPI1.0:RSDP1RSDTFADT1FACS1DSDTMADTSSDTHPET,怎样在ios中禁用acpi主板acpihpettaleacpihpettale要开吗suspendtoramlegacyussupportacpihpettale开启acpihpettale华擎acp,ACPIControlStructure(&#39FACS&#39)DSDTDifferentiatedSystemDescriptionTale(providedACPIspecch143.0EFIEnhancedFirmwareInterfaceH,然后随便触发一个中断就OK了再就是在开分页机制的(u32*)&quotHPET&quot)parseHpet((ACPIHeaderHpet*)[6u8oemTaleID[8u32oemVersionu,acpisrattaleacpitaleacpihpettaleios里面把acpiacpiios设置iosacpiios中尝试禁用acpiios关闭acpi2.0amiiosacpi2.0acpi,除了开双核还可以可以修复ACPI缺陷(不需要ACPI主要是由很多表(Tale)组成而DSDT(acpipatcher程序中cpufixhpetfixrtcfix三,这是有关ACPI(高级配置和电源接)的设置设置项有本选项是开启/关闭HPET设置项有Disaled(关闭)/,6acpiawaymode此选项用于设置是否启用acpiaway模式。7hpetsupport此选项用于设置是否启用hpet,硬件并且阐述了它们必须如何工作但是ACPI既不是一个DifferentiatedSystemDescriptionTale(DSDT)——HPETIAPCHighPrecisionEvent欢迎转载收藏,请保留我们的版权 无翼鸟漫画
acpi hpet table要开吗相关:您要找的是不是:
n. 宠物;生气;受宠爱的人 | vt. 宠爱 | v...
高精度事件定时器
Linux的计时体系结构还依赖于时间戳计数器(TSC)、ACPI电源管理定时器、高精度事件定时器(HPET)的可用性。内核使用两个基本的计时函数:一个保持当前最新的时间,另一个计算在当前秒内走过的纳秒数。
基于133个网页-
高精度计时器
关于linux内核中使用的时钟 ... 3):可编程中断定时器(PIC) 该设备可以周期性的发送一个时间中断信号.发送中断信号的间隔可以对其进行编程控制.在linux系统中,该中断时间间隔由HZ表示.这个时间间隔也被称为一个节拍(tick). 5):高精度计时器(HPET) ...
基于37个网页-
高精度定时器
搭配信息,ACPI包罗的配相信息许多,譬如多解决器配相信息(MADT)、NUMA配相信息(SRAT、SLIT)、高精度定时器(HPET)等。
基于20个网页-
高精度时间定时器
...主要采用可编程中断时钟(PIT)、本地APIC、时间戳计数器(Time Stamp Counter)、电源管理定时器(ACPI PMT)、高精度时间定时器(HPET)
PIT:一种可编程硬件设备,以固定频率(节拍率)自行触发定时器中断。系统启动时,内核对其进行编程初始化,设定其节拍率。
基于17个网页-
是否开启高精度定时器功能
高精度事件定时器
选择HPET的记忆地址
$firstVoiceSent
- 来自原声例句
请问您想要如何调整此模块?
感谢您的反馈,我们会尽快进行适当修改!
请问您想要如何调整此模块?
感谢您的反馈,我们会尽快进行适当修改!acpi 挂起到内存
ai为什么内存不足优化电脑系统内存的八大方法vivox6配置出炉配4g内存+全新hifi芯片手机内存不足清理电脑内存如何查看大家知道苹果6s的运行内存是多少的吗怎样挑选内存内存助手怎样下载电影到内存卡上?oppo内存满怎么办?手机运行内存到底消耗在哪里?学会这招让iphone自动清理内存内存时序的介绍php对象在内存中的分配清理内存的问题c/c++变量在内存中的分布堆栈区别堆栈段数据段代码段附加段透明到桌面qq音乐小内存文件拷贝到内存卡中就消失怎么办小米5splus运行内存是多大?电脑内存怎么清理
acpi 挂起到内存详情介绍:
其他名称:SuspendSTR(SuspendToRAM)挂起挂起到内存休眠计算机将目前在我的/etc/sysconfig/suspendscripts/中有一些脚本另外/etc/ac,ACPIFunction(初级电源管理)ACPISuspendType(系统挂起模式)PowerManagement(电流治理)基于48个网页相关网页ACPI挂起模式[推荐CMOS设置完全,S2S3:STR(SuspendToRam)即挂起到内存。系统把当前信息储存在内存中只有你可以从这里下载最新的ACPI补丁。Linux核心源代码目录:Documentation,挂起到内存相当于WINDOWS的Sleep[睡眠注S3当前不支持Kernel2.4.x。S4:Q:我已设置ACPI_SLEEP=true但仍然无法挂起?A:请查看你的laptop支持那,最佳答案:COMS设置中的一项ACPISuspendType(ACPI挂起模式)设置是否使用ACPI挂起模式设置为S1(POS)时CPU时钟停止工作而其他设备仍然供电功耗&lt30W设置更多关于acpi挂起到内存的问题&gt&gt,通过内存进行提供一般1024M内存选择的标准是64M/128M四、PowerManagementSetup电源管理设置(归南桥管理)ACPISuspendModeACPI高级电源,最佳答案:打了影驰的客服说ios没做自己也不能搞如果映的人多的话可以考虑升级ios供用户更新郁闷查看原帖&gt&gt更多关于acpi挂起到内存的问题&gt&gt,ACPISuspendType(ACPI挂起类型)此选项设定ACPI功能的节电模式。可选项有:S1存储在内存中的这些信息被用来将系统恢复到以前的状态。PowerManagement(电源更多关于acpi挂起到内存的问题&gt&gt,ACPIStateDescriptionS0正常工作状态S1CPU与RAM供电正常但CPU不执行指令S2比S1更深的一个睡眠层次这种模式通常不采用S3挂起到内存S4挂起到硬盘S5,通过刷入205版本IOS彻底解决N43sn系统中断问题(挂起acpi.sys进程法后续)华硕FX50JX4200这款电脑内存条是什么牌子的?举报只看此人赞评分,问题描述:安装虚拟光驱问题最佳答案:个人认为装完PowerManager驱动就自动开启该功能ACPI主要支持三种节电方式1、(suspend即挂起)显示屏自动断电只是主机通电。这时敲任意键即可恢复原来状态更多关于acpi挂起到内存的问题&gt&gt,7.睡眠状态:挂起、待机、休眠(到磁盘)ACPI定义了不用的睡眠状态。其中比较重要的是S1即待机S3即挂起到内存即挂起S4即挂起到磁盘即休眠它们,STR是SuspendToRam的缩写也就是我们常说的挂起到内存。具体地说作系统支持ACPI目前Windows98SE和Windows2000均支持ACPI但第一版的Windo,初识ACPI说道作系统的电源管理方式不能不介绍一下ACPI。它是作系统实现电源唤醒后作系统从内存中读取数据恢复到挂起前的状态。该方式又被称,最佳答案:ACPISuspendType(ACPI挂起类型)设置项用于选择采用节能方案的类型可选设置值有S1(POS)和S3(STR)两种。含义如下:POS(Power_OnSuspend)即带电更多关于acpi挂起到内存的问题&gt&gt,恢复时计算机从内存读出数据回到挂起前的状态恢复速度较快。一般笔记本在电池1。sudogedit/etc/default/acpisupport更改ENALE_LAPTOP_MOD,不凡修笔记本维修培训ACPI高级电源管理ACPI介绍?高级配置与电源接(Advanced?当进入S3(挂起到内存)、S4(挂起到硬盘)、S5(软关机)状态时这,是的待机就是(ACPI挂起模式)设置是否使用ACPI挂起模式设置为S1(POS也就是挂起到内存而此时电脑不在处理数据所以程序不会运行网络也不会,95MDGS21简体中文4ACPI配置挂起到內存选择禁用执行ACPI挂起类型S1。建议选择自动以实现ACPIS3节能。检查就绪位启用可只在硬盘就绪时于S3后,在系统休眠后立即有一个ACPI:lowlevelresume。。。的东西出现然后开始附上最后一次挂起和唤醒的dmesg输出:[欢迎转载收藏,请保留我们的版权 无翼鸟漫画
acpi 挂起到内存相关:博客访问: 12886
博文数量: 5
博客积分: 125
博客等级: 入伍新兵
技术积分: 75
注册时间:
分类: LINUX 00:07:42
@@@@@@@@@@@@@@@@@@@@@@@@  获取ACPI TABLE的方法  @@@@@@@@@@@@@@@@@@@@@@@
1. 首先要安装acpidump和iasl命令。
$ sudo apt-get install acpidump
$ sudo apt-get install iasl
$ sudo apt-get install pmtools
有的机器上需要安装pmtools才可以。
2. 导出ACPI的数据。
$ sudo cat /proc/acpi/dsdt > dstd.dat
$ sudo cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat
如果找不到该文件可以使用下面的命令:
$ sudo acpidump > acpi.dat
3. 分离各表格数据,会生成多个数据文件。
$ acpixtract -a acpi.dat
Acpi table [DSDT] -  41555 bytes written to DSDT.dat
Acpi table [FACS] -     64 bytes written to FACS.dat
Acpi table [FACP] -    116 bytes written to FACP.dat
Acpi table [APIC] -    132 bytes written to APIC.dat
Acpi table [ASF!] -     99 bytes written to ASF!.dat
Acpi table [MCFG] -     60 bytes written to MCFG.dat
Acpi table [TCPA] -     50 bytes written to TCPA.dat
Acpi table [SLIC] -    374 bytes written to SLIC.dat
Acpi table [HPET] -     56 bytes written to HPET.dat
Acpi table [DMAR] -    456 bytes written to DMAR.dat
Acpi table [RSDT] -     68 bytes written to RSDT.dat
Acpi table [RSDP] -     20 bytes written to RSDP.dat
4. 反汇编DSDT.dat,
$ iasl -d DSDT.dat
Intel ACPI Component Architecture
AML Disassembler version
[Oct 15 2010]
Copyright (c) 2000 - 2010 Intel Corporation
Supports ACPI Specification Revision 4.0a
Loading Acpi table from file DSDT.dat
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Parsing completed
Disassembly completed, written to "DSDT.dsl"
5. 根据需要修改DSDT.dsl文件,然后重新编译该文件,会生成DSDT.aml和DSDT.hex两个文件。
$ iasl -tc dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version
[Oct 15 2010]
Copyright (c) 2000 - 2010 Intel Corporation
Supports ACPI Specification Revision 4.0a
......................................................
ASL Input:  DSDT.dsl - 8762 lines, 320704 bytes, 3778 keywords
AML Output: DSDT.aml - 39328 bytes, 780 named objects, 2998 executable opcodes
Compilation complete. 0 Errors, 41 Warnings, 0 Remarks, 988 Optimizations
6. 更新DSDT的方法。
其一(没有测试过,不知道能否成功):
使用新的dsdt.aml代替BIOS中的版本:
    cp /boot/initrd.img-2.6.20-16-generic /boot/initrd.img-2.6.20-16-generic-bak
    sudo cp dsdt.aml /etc/initramfs-tools/DSDT.aml
    sudo update-initramfs -u -k all
其二(需要安装acpiexec,为找到):
iasl -sa DSDT.dsl        # e.g. recompile a modified, disassembled DSDT for
                           initramfs inclusion (see later)
acpiexec DSDT.dat        # parse, interpret and load a DSDT in userspace
这个方法需要重新编译内核。
首先将DSDT.hex文件复制到内核源码的include目录下。
$ cp DSDT.hex $SRC/include/
然后修改内核配置文件.config
    CONFIG_STANDALONE=n
    CONFIG_ACPI_CUSTOM_DSDT=y
    CONFIG_ACPI_CUSTOM_DSDT_FILE="DSDT.hex"
重新编译,更新内核,然后启动,可以在dmesg中看到
[    0.000000] ACPI: Override [DSDT- CDV-TPT], this is unsafe: tainting kernel
[    0.000000] Disabling lock debugging due to kernel taint
[    0.000000] ACPI: DSDT @ 0x7f378010 Table override, replaced with:
[    0.000000] ACPI: DSDT c0f0f140 0703F (v02  Intel  CDV-TPT
就说明DSDT已经被替换成修改过的了。
7. 在DSDT中添加LOG。
首先应该打开CONFIG_ACPI_DEBUG=y。
acpi.debug_level= ACPI_LV_DEBUG_OBJECT,
acpi.debug_layer= ACPI_TABLES | ACPI_NAMESPACE,
使用将想要的变量或者字符串赋值给Debug即可。
(Store (AAAA, Debug)
下面附上原文:
Dumping ACPI tables using acpidump and acpixtract
Most of the time when I'm looking at BIOS issues I just look at the disassembled ACPI DSDT using the following runes:
$ sudo cat /proc/acpi/dsdt > dstd.dat
$ iasl -d dstd.dat
..and look at the disassembly in dstd.dsl
Some BIOS bugs need a little more examination, and that's where I use acpidump + acpixtract. The simplest way to dump all the ACPI tables is as follows:
$ sudo acpidump > acpi.dat
$ acpixtract -a acpi.dat
Acpi table [DSDT] - 24564 bytes written to DSDT.dat
Acpi table [FACS] - 64 bytes written to FACS.dat
Acpi table [FACP] - 244 bytes written to FACP1.dat
Acpi table [APIC] - 104 bytes written to APIC1.dat
Acpi table [HPET] - 56 bytes written to HPET.dat
Acpi table [MCFG] - 60 bytes written to MCFG.dat
Acpi table [TCPA] - 50 bytes written to TCPA.dat
Acpi table [TMOR] - 38 bytes written to TMOR.dat
Acpi table [SLIC] - 374 bytes written to SLIC.dat
Acpi table [APIC] - 104 bytes written to APIC2.dat
Acpi table [BOOT] - 40 bytes written to BOOT.dat
Acpi table [SSDT] - 685 bytes written to SSDT1.dat
Acpi table [SSDT] - 163 bytes written to SSDT2.dat
Acpi table [SSDT] - 607 bytes written to SSDT3.dat
Acpi table [SSDT] - 166 bytes written to SSDT4.dat
Acpi table [SSDT] - 1254 bytes written to SSDT5.dat
Acpi table [XSDT] - 148 bytes written to XSDT.dat
Acpi table [FACP] - 116 bytes written to FACP2.dat
Acpi table [RSDT] - 88 bytes written to RSDT.dat
Acpi table [RSDP] - 36 bytes written to RSDP.dat
..this dumps out all the tables into files.
One can the disassemble the required file using iasl, e.g.:
$ iasl -d APIC1.dat
or decode the table using madt:
$ madt < ACPI1.dsl
ACPI: APIC (v001 INTEL CRESTLNE 0x LOHR 0x0000005a) @ 0x(nil)
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: IOAPIC (id[0x01] address[0xfec00000] global_irq_base[0x0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Length 104 OK
Checksum OK
Or to just get one particular table, I use:
$ sudo acpidump -t SSDT > SSDT.dat
$ acpixtract -a SSDT.dat
$ iasl -d SSDT.dat
Intel ACPI Component Architecture
AML Disassembler version
[Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file SSDT.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
Parsing completed
Disassembly completed, written to "SSDT.dsl"
Armed with a copy of the ACPI spec, one can then start digging into why there are weird Linux/BIOS interactions occurring.
How to Build a custom DSDT into the kernel
&#160;&#160;&#160; Get original DSDT:
&#160;&#160;&#160; # cp /proc/acpi/dsdt DSDT
&#160;&#160;&#160; or
&#160;&#160;&#160; # acpidump > acpidump.out
&#160;&#160;&#160; $ acpixtract DSDT acpidump > DSDT.dat
&#160;&#160;&#160; Disassemble it
&#160;&#160;&#160; $ iasl -d DSDT.dat
&#160;&#160;&#160; Make your changes:
&#160;&#160;&#160; $ vi DSDT.dsl
&#160;&#160;&#160; Build it:
&#160;&#160;&#160; $ iasl -tc DSDT.dsl
&#160;&#160;&#160; Put it where the kernel build can include it:
&#160;&#160;&#160; $ cp DSDT.hex $SRC/include/
&#160;&#160;&#160; Add this to the kernel .config:
&#160;&#160;&#160; CONFIG_STANDALONE=n
&#160;&#160;&#160; CONFIG_ACPI_CUSTOM_DSDT=y
&#160;&#160;&#160; CONFIG_ACPI_CUSTOM_DSDT_FILE="DSDT.hex"
&#160;&#160;&#160; Make the kernel and off you go!
&#160;&#160;&#160; You should see in dmesg:
&#160;&#160;&#160; Table [DSDT] replaced by host OS
@@@@@@@@@@@@@@@@@@@@@&#160; Linux ACPI Custom Control Method How To&#160; @@@@@@@@@@@@@@@@@@@@@@@
Written by Zhang Rui
Linux supports customizing ACPI control methods at runtime.
Users can use this to
1. override an existing method which may not work correctly, or just for debugging purposes.
2. insert a completely new method in order to create a missing method such as _OFF, _ON, _STA, _INI, etc. For these cases, it is far simpler to dynamically install a single control method rather than override the entire DSDT, because kernel rebuild/reboot is not needed and test result can be got in minutes.
Note: Only ACPI METHOD can be overridden, any other object types like "Device", "OperationRegion", are not recognized. Note: The same ACPI control method can be overridden for many times, and it's always the latest one that used by Linux/kernel. Note: To get the ACPI debug object output (Store (AAAA, Debug)), please run "echo 1 > /sys/module/acpi/parameters/aml_debug_output".
1. override an existing method a) get the ACPI table via ACPI sysfs I/F. e.g. to get the DSDT, just run "cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat" b) disassemble the table by running "iasl -d dsdt.dat".
&#160;&#160; c) rewrite the ASL code of the method and save it in a new file,
&#160;&#160; d) package the new file (psr.asl) to an ACPI table format. Here is an example of a customized \_SB._AC._PSR method,
&#160;&#160;&#160;&#160;&#160; DefinitionBlock ("", "SSDT", 1, "", "", 0x)
&#160;&#160;&#160;&#160;&#160; { External (ACON)
Method (\_SB_.AC._PSR, 0, NotSerialized)
{ Store ("In AC _PSR", Debug)
Return (ACON) } }
&#160;&#160;&#160;&#160;&#160; Note that the full pathname of the method in ACPI namespace
&#160;&#160;&#160;&#160;&#160; should be used.
&#160;&#160;&#160;&#160;&#160; And remember to use "External" to declare external objects. e) assemble the file to generate the AML code of the method. e.g. "iasl psr.asl" (psr.aml is generated as a result) f) mount debugfs by "mount -t debugfs none /sys/kernel/debug"
&#160;&#160; g) override the old method via the debugfs by running "cat /tmp/psr.aml > /sys/kernel/debug/acpi/custom_method"
2. insert a new method This is easier than overriding an existing method.
&#160;&#160; We just need to create the ASL code of the method we want to
&#160;&#160; insert and then follow the step c) ~ g) in section 1.
3. undo your changes The "undo" operation is not supported for a new inserted method
&#160;&#160; right now, i.e. we can not remove a method currently.
&#160;&#160; For an overrided method, in order to undo your changes, please
&#160;&#160; save a copy of the method original ASL code in step c) section 1,
&#160;&#160; and redo step c) ~ g) to override the method with the original one.
Note: We can use a kernel with multiple custom ACPI method running, But each individual write to debugfs can implement a SINGLE
&#160;&#160;&#160;&#160;&#160; method override. i.e. if we want to insert/override multiple
&#160;&#160;&#160;&#160;&#160; ACPI methods, we need to redo step c) ~ g) for multiple times.
Note: Be aware that root can mis-use this driver to modify arbitrary memory and gain additional rights, if root's privileges got
&#160;&#160;&#160;&#160;&#160; restricted (for example if root is not allowed to load additional modules after boot).
/sys/module/acpi/parameters/:
trace_method_name The AML method name that the user wants to trace
trace_debug_layer The temporary debug_layer used when tracing the method.
Using 0xffffffff by default if it is 0.
trace_debug_level The temporary debug_level used when tracing the method.
Using 0x00ffffff by default if it is 0.
trace_state The status of the tracing feature.
"enabled" means this feature is enabled
and the AML method is traced every time it's executed.
"1" means this feature is enabled and the AML method
will only be traced during the next execution.
"disabled" means this feature is disabled.
Users can enable/disable this debug tracing feature by
"echo string > /sys/module/acpi/parameters/trace_state".
"string" should be one of "enable", "disable" and "1".
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&#160; ACPI Debug Output&#160; @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ACPI CA, the Linux ACPI core, and some ACPI drivers can generate debug output.&#160; This document describes how to use this facility.
Compile-time configuration
--------------------------
ACPI debug output is globally enabled by CONFIG_ACPI_DEBUG.&#160; If this config option is turned off, the debug messages are not even built into the kernel.
Boot- and run-time configuration
--------------------------------
When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages you're interested in.&#160; At boot-time, use the acpi.debug_layer and acpi.debug_level kernel command line options.&#160; After boot, you can use the debug_layer and debug_level files in /sys/module/acpi/parameters/ to control the debug messages.
debug_layer (component)
-----------------------
The "debug_layer" is a mask that selects components of interest, e.g., a specific driver or part of the ACPI interpreter.&#160; To build the debug_layer bitmask, look for the "#define _COMPONENT" in an ACPI source file.
You can set the debug_layer mask at boot-time using the acpi.debug_layer command line argument, and you can change it after boot by writing values to /sys/module/acpi/parameters/debug_layer.
The possible components are defined in include/acpi/acoutput.h and include/acpi/acpi_drivers.h.&#160; Reading /sys/module/acpi/parameters/debug_layer shows the supported mask values, currently these:
&#160;&#160;&#160; ACPI_UTILITIES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_HARDWARE&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_EVENTS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_TABLES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_NAMESPACE&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_PARSER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_DISPATCHER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_EXECUTER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_RESOURCES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_CA_DEBUGGER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_OS_SERVICES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_CA_DISASSEMBLER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_COMPILER&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_TOOLS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_BUS_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_AC_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_BATTERY_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_BUTTON_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_SBS_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_FAN_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_PCI_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_POWER_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_CONTAINER_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_SYSTEM_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_THERMAL_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x ACPI_MEMORY_DEVICE_COMPONENT&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_VIDEO_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_PROCESSOR_COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
debug_level
-----------
The "debug_level" is a mask that selects different types of messages, e.g., those related to initialization, method execution, informational messages, etc. To build debug_level, look at the level specified in an ACPI_DEBUG_PRINT() statement.
The ACPI interpreter uses several different levels, but the Linux ACPI core and ACPI drivers generally only use ACPI_LV_INFO.
You can set the debug_level mask at boot-time using the acpi.debug_level command line argument, and you can change it after boot by writing values to /sys/module/acpi/parameters/debug_level.
The possible levels are defined in include/acpi/acoutput.h.&#160; Reading /sys/module/acpi/parameters/debug_level shows the supported mask values, currently these:
&#160;&#160;&#160; ACPI_LV_INIT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_DEBUG_OBJECT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_INFO&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_INIT_NAMES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_PARSE&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_LOAD&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_DISPATCH&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_EXEC&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_NAMES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_OPREGION&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_BFIELD&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_TABLES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_VALUES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_OBJECTS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_RESOURCES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_USER_REQUESTS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_PACKAGE&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_ALLOCATIONS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_FUNCTIONS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_OPTIMIZATIONS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_MUTEX&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_THREADS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_IO&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_INTERRUPTS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_AML_DISASSEMBLE&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_VERBOSE_INFO&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_FULL_TABLES&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
&#160;&#160;&#160; ACPI_LV_EVENTS&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 0x
For example, drivers/acpi/bus.c contains this:
&#160;&#160;&#160; #define _COMPONENT&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; ACPI_BUS_COMPONENT
&#160;&#160;&#160; ...
&#160;&#160;&#160; ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Device insertion detected\n"));
To turn on this message, set the ACPI_BUS_COMPONENT bit in acpi.debug_layer and the ACPI_LV_INFO bit in acpi.debug_level.&#160; (The ACPI_DEBUG_PRINT statement uses ACPI_DB_INFO, which is macro based on the ACPI_LV_INFO definition.)
Enable all AML "Debug" output (stores to the Debug object while interpreting AML) during boot:
&#160;&#160;&#160; acpi.debug_layer=0xffffffff acpi.debug_level=0x2
Enable PCI and PCI interrupt routing debug messages:
&#160;&#160;&#160; acpi.debug_layer=0x400000 acpi.debug_level=0x4
Enable all ACPI hardware-related messages:
&#160;&#160;&#160; acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
Enable all ACPI_DB_INFO messages after boot:
&#160;&#160;&#160; # echo 0x4 > /sys/module/acpi/parameters/debug_level
Show all valid component values:
&#160;&#160;&#160; # cat /sys/module/acpi/parameters/debug_layer
阅读(1635) | 评论(0) | 转发(0) |
下一篇:没有了
给主人留下些什么吧!~~
请登录后评论。}

我要回帖

更多关于 acpi hpet开启 的文章

更多推荐

版权声明:文章内容来源于网络,版权归原作者所有,如有侵权请点击这里与我们联系,我们将及时删除。

点击添加站长微信