From: Len Brown <len.brown@intel.com>
To: Bjoern Schmidt <lucky21@uni-paderborn.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fsb of older cpu
Date: 09 Mar 2004 23:17:53 -0500 [thread overview]
Message-ID: <1078892273.2347.551.camel@dhcppc4> (raw)
In-Reply-To: <404DA7A8.4090109@uni-paderborn.de>
> root@kilobyte:/proc/acpi/processor/C097# cat power
> active state: C2
> default state: C1
> bus master activity: 00000000
> states:
> C1: promotion[C2] demotion[--] latency[000] usage[00000240]
> *C2: promotion[--] demotion[C1] latency[100] usage[169083068]
> C3: <not supported>
latency is in microseconds. 100 is the highest latency C2 can have w/o
being disabled entirely. (eg. my laptop has C2 latency of 1, and C3
latency of 85) Though it is not uncommon for desktop chips to not
support C2 at all...
> Do you know a little program to visualize the fadt flags in a human
> readable way?
# cat /proc/acpi/fadt | ~lenb/bin/acpitbl
where acpitbl is a script in pmtools:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
will print something like this, which depending on the human, is
readable;-)
Signature: FACP
Length: 132
Revision: 0x02
Checksum: 0x58
OEMID: TOSHIB
OEM Table ID: 750
OEM Revision: 0x20030101
Creator ID: TASM
Creator Revision: 0x04010000
FIRMWARE_CTRL: 0x000eee00
DSDT: 0x1ffd0114
INT_MODEL: 0x00
SCI_INT: 9
SMI_CMD: 0x000000b2
ACPI_ENABLE: 0x71
ACPI_DISABLE: 0x70
S4BIOS_REQ: 0x72
PM1a_EVT_BLK: 0x0000d800
PM1b_EVT_BLK: 0x00000000
PM1a_CNT_BLK: 0x0000d804
PM1b_CNT_BLK: 0x00000000
PM2_CNT_BLK: 0x0000d820
PM_TMR_BLK: 0x0000d808
GPE0_BLK: 0x0000d828
GPE1_BLK: 0x00000000
PM1_EVT_LEN: 4
PM1_CNT_LEN: 2
PM2_CNT_LEN: 1
PM_TM_LEN: 4
GPE0_BLK_LEN: 8
GPE1_BLK_LEN: 0
GPE1_BASE: 0
P_LVL2_LAT: 1
P_LVL3_LAT: 85
FLUSH_SIZE: 0
FLUSH_STRIDE: 0
DUTY_OFFSET: 1
DUTY_WIDTH: 0
DAY_ALRM: 0x0d
MON_ALRM: 0x7e
CENTURY: 0x00
Flags: 0x000004a5
next prev parent reply other threads:[~2004-03-10 4:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F47CB@hdsmsx402.hd.intel.com>
2004-03-09 6:58 ` fsb of older cpu Len Brown
2004-03-09 11:16 ` Bjoern Schmidt
2004-03-09 11:35 ` Stefan Smietanowski
2004-03-09 12:07 ` Bjoern Schmidt
2004-03-10 4:17 ` Len Brown [this message]
2004-03-11 13:53 ` [BUG] " Bjoern Schmidt
2004-03-14 15:11 ` Bjoern Schmidt
2004-03-08 10:38 Bjoern Schmidt
2004-03-08 16:14 ` Bernd Schubert
2004-03-08 20:17 ` Bjoern Schmidt
2004-03-08 20:46 ` Zwane Mwaikambo
2004-03-08 21:14 ` Stefan Smietanowski
2004-03-08 23:06 ` Zwane Mwaikambo
2004-03-08 21:09 ` Stefan Smietanowski
2004-03-08 21:53 ` Bjoern Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1078892273.2347.551.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucky21@uni-paderborn.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.