From: Dave Jones <davej@redhat.com>
To: Dan Hollis <goemon@anime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bizarre 2.6.8.1 /sys permissions
Date: Thu, 26 Aug 2004 01:48:57 +0100 [thread overview]
Message-ID: <20040826004857.GA5583@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0408251630380.17580-100000@sasami.anime.net>
On Wed, Aug 25, 2004 at 04:31:50PM -0700, Dan Hollis wrote:
> > > $ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
> > > cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: Permission denied
> > Reading this file causes reads from hardware on some cpufreq drivers.
> > This can be a slow operation, so a user could degrade system performance
> > for everyone else by repeatedly cat'ing it.
>
> any reason why cpuinfo_cur_freq cant read cpu_khz ?
cpufreq_cur_freq will be one of scaling_available_frequencies.
These are usually a value such as 1300MHz, where cpu_mhz is a
'measured' value and will look something like 1303.852
the values cpufreq uses are the values either returned by the
hardware as its settable states, or from BIOS tables defining
those states.
> or rather, is there any reason why cpuinfo_cur_freq and /proc/cpuinfo
> should legitimately differ?
They aren't identical, and serve different purposes.
Dave
next prev parent reply other threads:[~2004-08-26 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 20:25 bizarre 2.6.8.1 /sys permissions Dan Hollis
2004-08-25 22:18 ` Dave Jones
2004-08-25 23:31 ` Dan Hollis
2004-08-26 0:48 ` Dave Jones [this message]
2004-08-26 19:00 ` Bill Davidsen
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=20040826004857.GA5583@redhat.com \
--to=davej@redhat.com \
--cc=goemon@anime.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox