linux-kernel - Re: [PATCH v2] intel_idle: add idle values for Cherrytrail/Braswell

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:	Mon, 25 Aug 2014 13:12:00 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	"Li, Aubrey" <aubrey.li@...ux.intel.com>
Cc:	Len Brown <lenb@...nel.org>,
	Kumar P Mahesh <mahesh.kumar.p@...el.com>,
	Alan Cox <alan@...ux.intel.com>, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] intel_idle: add idle values for Cherrytrail/Braswell

On Fri, Aug 22, 2014 at 10:06:21PM +0800, Li, Aubrey wrote:
> On 2014/8/22 19:39, Mika Westerberg wrote:
> > From: Mahesh Kumar P <mahesh.kumar.p@...el.com>
> > 
> > Cherrytrail/Braswell is a successor of Intel Baytrail but has slighly
> > different CPU idle values and latencies.
> > 
> > Signed-off-by: Kumar P Mahesh <mahesh.kumar.p@...el.com>
> > Signed-off-by: Alan Cox <alan@...ux.intel.com>
> > Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
> > ---
> > I learned from Mahesh that C1e, C4 and S0i2 states are deprecated so those
> > are now removed.
> 
> If the platform has ACPI supported, I believe Len wants to see what
> C-states number exported by ACPI.
> 
> Please boot the machine with "intel_idle.max_cstate=0" to disable
> intel_idle, then post the output of the following commands

OK, here goes:

> dmesg | grep idle

[    0.523624] cpuidle: using governor ladder
[    0.528215] cpuidle: using governor menu
[   16.649461] intel_idle: disabled
[   16.736481] ACPI: acpi_idle registered with cpuidle

> grep . /sys/devices/system/cpu/cpu0/cpuidle/*/*

/sys/devices/system/cpu/cpu0/cpuidle/state0/desc:CPUIDLE CORE POLL IDLE
/sys/devices/system/cpu/cpu0/cpuidle/state0/disable:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/name:POLL
/sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295
/sys/devices/system/cpu/cpu0/cpuidle/state0/residency:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/time:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/usage:0
/sys/devices/system/cpu/cpu0/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0
/sys/devices/system/cpu/cpu0/cpuidle/state1/disable:0
/sys/devices/system/cpu/cpu0/cpuidle/state1/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1
/sys/devices/system/cpu/cpu0/cpuidle/state1/power:0
/sys/devices/system/cpu/cpu0/cpuidle/state1/residency:2
/sys/devices/system/cpu/cpu0/cpuidle/state1/time:1255076
/sys/devices/system/cpu/cpu0/cpuidle/state1/usage:763
/sys/devices/system/cpu/cpu0/cpuidle/state2/desc:ACPI FFH INTEL MWAIT 0x58
/sys/devices/system/cpu/cpu0/cpuidle/state2/disable:0
/sys/devices/system/cpu/cpu0/cpuidle/state2/latency:500
/sys/devices/system/cpu/cpu0/cpuidle/state2/name:C2
/sys/devices/system/cpu/cpu0/cpuidle/state2/power:0
/sys/devices/system/cpu/cpu0/cpuidle/state2/residency:1000
/sys/devices/system/cpu/cpu0/cpuidle/state2/time:1694866
/sys/devices/system/cpu/cpu0/cpuidle/state2/usage:639
/sys/devices/system/cpu/cpu0/cpuidle/state3/desc:ACPI FFH INTEL MWAIT 0x64
/sys/devices/system/cpu/cpu0/cpuidle/state3/disable:0
/sys/devices/system/cpu/cpu0/cpuidle/state3/latency:5000
/sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3
/sys/devices/system/cpu/cpu0/cpuidle/state3/power:0
/sys/devices/system/cpu/cpu0/cpuidle/state3/residency:10000
/sys/devices/system/cpu/cpu0/cpuidle/state3/time:380547473
/sys/devices/system/cpu/cpu0/cpuidle/state3/usage:744
--
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/