From: Russell King <rmk@arm.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Matt Dainty <matt@bodgit-n-scarper.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)
Date: Sun, 6 Jan 2002 21:36:19 +0000 [thread overview]
Message-ID: <20020106213619.C7654@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020106181749.A714@butterlicious.bodgit-n-scarper.com> <200201061934.g06JYnZ15633@vindaloo.ras.ucalgary.ca> <3C38BC6B.7090301@zytor.com> <200201062108.g06L8lM17189@vindaloo.ras.ucalgary.ca> <3C38BD32.6000900@zytor.com>
In-Reply-To: <3C38BD32.6000900@zytor.com>; from hpa@zytor.com on Sun, Jan 06, 2002 at 01:10:10PM -0800
On Sun, Jan 06, 2002 at 01:10:10PM -0800, H. Peter Anvin wrote:
> The existence of a CPU creates /dev/cpu/# and registering a node
> replicates across the /dev/cpu directories.
And, thus, we decend into more /proc crappyness.
After *lots* of discussion and months of waiting, it was decided between
Alan, David Jones, Jeff Garzik, and other affected parties that
/proc/sys/cpu/#/whatever would be a reasonable. It has even appeared on
lkml a couple of times in the past.
Currently, there is an allocated sysctl number in include/linux/sysctl.h
for /proc/sys/cpu, and it is used by the cpufreq code to provide:
/proc/sys/cpu/#/speed
/proc/sys/cpu/#/speed-max
/proc/sys/cpu/#/speed-min
However, it's true that some of that needs to be pulled out so anything
can use /proc/sys/cpu/#. Just takes the necessary parties to get together
to do the hard work, and with the right hardware to test it out.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-01-06 21:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 18:17 [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr) Matt Dainty
2002-01-06 19:34 ` Richard Gooch
2002-01-06 20:43 ` Matt Dainty
2002-01-06 21:08 ` H. Peter Anvin
2002-01-06 21:11 ` Richard Gooch
2002-01-06 21:12 ` H. Peter Anvin
2002-01-06 21:06 ` H. Peter Anvin
2002-01-06 21:08 ` Richard Gooch
2002-01-06 21:10 ` H. Peter Anvin
2002-01-06 21:36 ` Russell King [this message]
2002-01-07 0:44 ` H. Peter Anvin
2002-01-07 1:31 ` Richard Gooch
2002-01-07 1:32 ` H. Peter Anvin
2002-01-07 1:40 ` Richard Gooch
2002-01-07 1:44 ` H. Peter Anvin
2002-01-08 11:13 ` Matt Dainty
2002-01-08 9:14 ` Rusty Russell
2002-01-08 12:02 ` Matt Dainty
2002-01-08 17:35 ` Richard Gooch
2002-01-08 17:17 ` H. Peter Anvin
2002-01-09 1:01 ` Rusty Russell
2002-01-09 3:16 ` H. Peter Anvin
2002-01-09 3:28 ` Rusty Russell
2002-01-09 3:30 ` Richard Gooch
2002-01-09 3:47 ` H. Peter Anvin
2002-01-09 5:41 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 10:50 Ishan Jayawardena
2002-02-18 18:25 ` Richard Gooch
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=20020106213619.C7654@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@bodgit-n-scarper.com \
--cc=rgooch@ras.ucalgary.ca \
/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.