From: ian.soboroff@nist.gov
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 - cpu_freg sysfs nodes?
Date: Tue, 15 Jul 2003 14:17:23 -0400 [thread overview]
Message-ID: <m3d6gb1wp8.fsf@euphrates.ncsl.nist.gov> (raw)
In-Reply-To: <20030715164251.GA2623@inferi.kami.home> (Mattia Dongili's message of "Tue, 15 Jul 2003 18:42:51 +0200")
Mattia Dongili <dongili@supereva.it> writes:
> find /sys -iname 'cpu*'
>
> /sys/firmware/acpi/namespace/ACPI/CPU0
> /sys/devices/system/cpu
> /sys/devices/system/cpu/cpu0
> /sys/devices/system/cpu/cpu0/cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
If this is the right place to look, the Documentation/cpu-freq needs
some updating.
But this still isn't it...
# find /sys -iname 'cpu*'
/sys/devices/system/cpu
/sys/devices/system/cpu/cpu0
/sys/cdev/major/cpu!cpuid
/sys/cdev/major/cpu!msr
:-(
Ian
next prev parent reply other threads:[~2003-07-15 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 17:12 2.6.0-test1 - cpu_freg sysfs nodes? ian.soboroff
2003-07-15 16:42 ` Mattia Dongili
2003-07-15 18:17 ` ian.soboroff [this message]
2003-07-15 17:48 ` Dave Jones
2003-07-15 17:50 lkml
2003-07-15 20:50 ` ian.soboroff
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=m3d6gb1wp8.fsf@euphrates.ncsl.nist.gov \
--to=ian.soboroff@nist.gov \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).