lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 5 Feb 2008 02:16:54 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Shaohua Li <shaohua.li@...el.com>
Subject: Re: Why do I have a /sys/devices/system/cpu/cpuidle under kernel
 2.6.24 with a Pentium M processor ?

On Thu, 31 Jan 2008 14:00:14 +0100 Toralf Förster <toralf.foerster@....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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ