All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Rendec <radu.rendec@mindbit.ro>
To: cpufreq@vger.kernel.org
Subject: sysfs support for scaling_cur_freq in intel_pstate
Date: Tue, 06 Aug 2013 00:37:43 +0300	[thread overview]
Message-ID: <1375738663.6273.56.camel@localhost> (raw)

Hi!

After a recent kernel upgrade on my laptop I noticed that my cpu
frequency desktop applet wasn't working anymore. I quickly tracked down
the problem to the fact that the new scaling driver was intel_pstate,
and it didn't expose scaling_cur_freq in sysfs.

On the other hand, cpuinfo_cur_freq is available, but it's only readable
by root. Apparently there are good reasons for keeping it like this. I
found an older post about this here:
http://comments.gmane.org/gmane.linux.kernel.cpufreq/7005

However, looking at the code in intel_pstate.c, it seems that
intel_pstate_get() (which is the implementation for cpuinfo_cur_freq in
sysfs) simply extracts a value out of a larger structure. This seems
really harmless and very far away from the reasons why cpuinfo_cur_freq
was kept readable by root only.

Looking at cpufreq_add_dev_interface() in cpufreq.c, it seems that one
needs to define the "target" field in struct cpufreq_driver in order to
have scaling_cur_freq exposed in sysfs.

I think setting "target" to intel_pstate_get() in the definition of
intel_pstate_driver would fix my problem, since scaling_cur_freq in
sysfs is world readable. Is there any reason for not doing this?

If you reply, please cc my personal address - I'm not subscribed to the
list.

Thanks,

Radu Rendec



             reply	other threads:[~2013-08-05 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 21:37 Radu Rendec [this message]
2013-08-05 22:25 ` sysfs support for scaling_cur_freq in intel_pstate Rafael J. Wysocki

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=1375738663.6273.56.camel@localhost \
    --to=radu.rendec@mindbit.ro \
    --cc=cpufreq@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.