From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 57941] Cpufreq stats are not shown in sysfs
Date: Sun, 12 May 2013 16:16:51 +0000 (UTC) [thread overview]
Message-ID: <20130512161651.9C72211F943@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-57941-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=57941
--- Comment #2 from Justin <jlec@gentoo.org> 2013-05-12 16:16:51 ---
(In reply to comment #1)
> Only this one is missing or complete stats directory?
You are right. The complete directory is missing.
# ll /sys/devices/system/cpu/cpu0/cpufreq/
total 0
-r--r--r-- 1 root root 4.0K May 12 18:16 affected_cpus
-r-------- 1 root root 4.0K May 12 18:16 cpuinfo_cur_freq
-r--r--r-- 1 root root 4.0K May 12 11:26 cpuinfo_max_freq
-r--r--r-- 1 root root 4.0K May 12 11:26 cpuinfo_min_freq
-r--r--r-- 1 root root 4.0K May 12 18:16 cpuinfo_transition_latency
-r--r--r-- 1 root root 4.0K May 12 18:16 related_cpus
-r--r--r-- 1 root root 4.0K May 12 18:16 scaling_available_governors
-r--r--r-- 1 root root 4.0K May 12 18:16 scaling_driver
-rw-r--r-- 1 root root 4.0K May 12 18:16 scaling_governor
-rw-r--r-- 1 root root 4.0K May 12 11:26 scaling_max_freq
-rw-r--r-- 1 root root 4.0K May 12 18:16 scaling_min_freq
-rw-r--r-- 1 root root 4.0K May 12 18:16 scaling_setspeed
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-12 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 12:07 [Bug 57941] New: Cpufreq stats are not shown in sysfs bugzilla-daemon
2013-05-12 15:18 ` Viresh Kumar
2013-05-12 15:18 ` [Bug 57941] " bugzilla-daemon
2013-05-12 16:16 ` bugzilla-daemon [this message]
2013-05-13 2:00 ` bugzilla-daemon
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=20130512161651.9C72211F943@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.