linux-kernel - [v3.10-rc] intel

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]

Message-ID: <CADDKRnDH130wn8nVaT4xmCuEEcsGyBcjhj7pDjPMkeucUW+EWw@mail.gmail.com>
Date:	Tue, 28 May 2013 17:02:16 +0200
From:	Jörg Otte <jrg.otte@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	dirk.j.brandewie@...el.com, rafael.j.wysocki@...el.com
Subject: [v3.10-rc] intel_pstate question

Hi,

the sysfs-interface of intel_pstate is different to that of the acpi driver:
- intel_pstate shows current cpu-frequency in "cpuinfo_cur_freq" whereas
  the acpi counterpart uses "scaling_cur_freq".
- moreover cpuinfo_cur_freq is readable by root only, whereas
  scaling_cur_freq is world readable.

  A monitoring tool must take care of theese differences.
  Is this intentional?

Thanks, Jörg

Please CC me in answeres, I'm not subscribed.
--
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/