From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Dainty <matt@bodgit-n-scarper.com>
Cc: rgooch@ras.ucalgary.ca, hpa@zytor.com,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)
Date: Tue, 8 Jan 2002 20:14:51 +1100 [thread overview]
Message-ID: <20020108201451.088f7f99.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20020108111302.A14860@mould.bodgit-n-scarper.com>
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> <200201070131.g071VrM20956@vindaloo.ras.ucalgary.ca> <3C38FAB0.4000503@zytor.com> <200201070140.g071ewk21192@vindaloo.ras.ucalgary.ca> <20020108111302.A14860@mould.bodgit-n-scarper.com>
On Tue, 8 Jan 2002 11:13:02 +0000
Matt Dainty <matt@bodgit-n-scarper.com> wrote:
> On Sun, Jan 06, 2002 at 06:40:58PM -0700, Richard Gooch wrote:
> >
> > So I'd like to propose a new file (say kernel/smp.c) which has generic
> > startup code for each CPU. To start with, it can have a
> > generic_cpu_init() function, which is called by each arch. Note that
> > this function would be called for the boot CPU too.
>
> Would this also be hacked into whatever Hotswap CPU support exists? Such
We use /proc/sys/cpu/#/. I don't understand what /dev/cpu/xxx is supposed to
do.
It's unfortunate that /proc/sys and /proc suck so hard that good coders go
to great lengths to do anything else [see previous /proc/sys patches].
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-01-08 11:17 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
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 [this message]
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=20020108201451.088f7f99.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@bodgit-n-scarper.com \
--cc=rgooch@ras.ucalgary.ca \
--cc=torvalds@transmeta.com \
/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.