From: Andrew Morton <akpm@linux-foundation.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Shaohua Li <shaohua.li@intel.com>
Subject: Re: Why do I have a /sys/devices/system/cpu/cpuidle under kernel 2.6.24 with a Pentium M processor ?
Date: Tue, 5 Feb 2008 02:16:54 -0800 [thread overview]
Message-ID: <20080205021654.37286791.akpm@linux-foundation.org> (raw)
In-Reply-To: <200801311400.17811.toralf.foerster@gmx.de>
On Thu, 31 Jan 2008 14:00:14 +0100 Toralf Förster <toralf.foerster@gmx.de> wrote:
(suitable cc's added)
> I'm asking b/c this confuses the current sysstat up to version 8.0.4. An
That would be bad. Please define "confuses"?
> $ ls -lR /sys/devices/system/cpu/
>
> gives :
>
> /sys/devices/system/cpu/:
> total 0
> drwxr-xr-x 4 root root 0 Jan 30 09:36 cpu0
> drwxr-xr-x 2 root root 0 Jan 30 09:36 cpuidle
>
> /sys/devices/system/cpu/cpu0:
> total 0
> drwxr-xr-x 3 root root 0 Jan 30 09:36 cpufreq
> drwxr-xr-x 5 root root 0 Jan 30 09:36 cpuidle
>
> /sys/devices/system/cpu/cpu0/cpufreq:
> total 0
> -r--r--r-- 1 root root 4096 Jan 30 09:36 affected_cpus
> -r-------- 1 root root 4096 Jan 30 09:36 cpuinfo_cur_freq
> -r--r--r-- 1 root root 4096 Jan 30 09:36 cpuinfo_max_freq
> -r--r--r-- 1 root root 4096 Jan 30 09:36 cpuinfo_min_freq
> drwxr-xr-x 2 root root 0 Jan 30 09:36 ondemand
> -r--r--r-- 1 root root 4096 Jan 30 09:36 scaling_available_frequencies
> -r--r--r-- 1 root root 4096 Jan 30 09:36 scaling_available_governors
> -r--r--r-- 1 root root 4096 Jan 30 09:36 scaling_cur_freq
> -r--r--r-- 1 root root 4096 Jan 30 09:36 scaling_driver
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 scaling_governor
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 scaling_max_freq
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 scaling_min_freq
>
> /sys/devices/system/cpu/cpu0/cpufreq/ondemand:
> total 0
> -rw-r--r-- 1 root root 0 Jan 30 09:36 ignore_nice_load
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 powersave_bias
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 sampling_rate
> -r--r--r-- 1 root root 4096 Jan 30 09:36 sampling_rate_max
> -r--r--r-- 1 root root 4096 Jan 30 09:36 sampling_rate_min
> -rw-r--r-- 1 root root 4096 Jan 30 09:36 up_threshold
>
> /sys/devices/system/cpu/cpu0/cpuidle:
> total 0
> drwxr-xr-x 2 root root 0 Jan 30 09:36 state0
> drwxr-xr-x 2 root root 0 Jan 30 09:36 state1
> drwxr-xr-x 2 root root 0 Jan 30 09:36 state2
>
> /sys/devices/system/cpu/cpu0/cpuidle/state0:
> total 0
> -r--r--r-- 1 root root 4096 Jan 30 09:36 latency
> -r--r--r-- 1 root root 4096 Jan 30 09:36 name
> -r--r--r-- 1 root root 4096 Jan 30 09:36 power
> -r--r--r-- 1 root root 4096 Jan 30 09:36 time
> -r--r--r-- 1 root root 4096 Jan 30 09:36 usage
>
> /sys/devices/system/cpu/cpu0/cpuidle/state1:
> total 0
> -r--r--r-- 1 root root 4096 Jan 30 09:36 latency
> -r--r--r-- 1 root root 4096 Jan 30 09:36 name
> -r--r--r-- 1 root root 4096 Jan 30 09:36 power
> -r--r--r-- 1 root root 4096 Jan 30 09:36 time
> -r--r--r-- 1 root root 4096 Jan 30 09:36 usage
>
> /sys/devices/system/cpu/cpu0/cpuidle/state2:
> total 0
> -r--r--r-- 1 root root 4096 Jan 30 09:36 latency
> -r--r--r-- 1 root root 4096 Jan 30 09:36 name
> -r--r--r-- 1 root root 4096 Jan 30 09:36 power
> -r--r--r-- 1 root root 4096 Jan 30 09:36 time
> -r--r--r-- 1 root root 4096 Jan 30 09:36 usage
>
> /sys/devices/system/cpu/cpuidle:
> total 0
> -r--r--r-- 1 root root 4096 Jan 30 09:36 current_driver
> -r--r--r-- 1 root root 4096 Jan 30 09:36 current_governor_ro
>
> --
> MfG/Sincerely
>
> Toralf Förster
> pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
>
next prev parent reply other threads:[~2008-02-05 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 13:00 Toralf Förster
2008-02-05 10:16 ` Andrew Morton [this message]
2008-02-05 14:38 ` Toralf Förster
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=20080205021654.37286791.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=toralf.foerster@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®