linux-kernel - Re: AMD Bobcat cpufreq

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-next>] [day] [month] [year] [list]

Date:	Fri, 18 Oct 2013 16:19:49 +0300 (EEST)
From:	Joonas Saarinen <jza@...nalahti.fi>
To:	Borislav Petkov <bp@...en8.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: AMD Bobcat cpufreq

Borislav Petkov [bp@...en8.de] wrote:
> Once you've done that successfully, you need to run as root:
> 
> $ cd tools/power/cpupower/
> $ LD_LIBRARY_PATH=. ./cpupower frequency-info

This is what I get:

analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  hardware limits: 800 MHz - 1000 MHz
  available frequency steps: 1000 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 800 MHz and 1000 MHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 1000 MHz:-nan%, 800 MHz:-nan%  (646)
  boost state support:
    Supported: yes
    Active: yes

It's promising that the boost state support is "supported and active" 
but the output is still kind of sparse. There's no mention about
specific turbo states, nor do I get /proc/cpuinfo or that cpupower tool
ever to show an evidence that the CPU is going to 1333MHz. On Windows
CPU-Z showed it constantly visiting that state.

That's all for now.

Joonas

--
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/