All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matt Dainty <matt@bodgit-n-scarper.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Richard Gooch <rgooch@ras.ucalgary.ca>
Subject: Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)
Date: Sun, 06 Jan 2002 13:08:54 -0800	[thread overview]
Message-ID: <3C38BCE6.3030302@zytor.com> (raw)
In-Reply-To: <20020106181749.A714@butterlicious.bodgit-n-scarper.com> <200201061934.g06JYnZ15633@vindaloo.ras.ucalgary.ca> <20020106204311.C2596@butterlicious.bodgit-n-scarper.com>

Matt Dainty wrote:

> Okey dokey,
> 
> Please find attached a second, better patch to add devfs support to the i386
> cpuid and msr drivers. Now it doesn't nuke the cpu/X directories on
> unloading and only enumerates CPUs based on smp_num_cpus instead of NR_CPUS.
> 


If you don't understand why this is idiotic, then let me enlighten you: 
there is no sensible reason why /dev/cpu/%d should only be populated 
after having run a CPU-dependent device driver.  /dev/cpu/%d should be 
always populated; heck, that's the only way you can sensibly handle 
hotswapping CPUs.

I WILL NOT accept a patch as long as devfs is as fucked in the head as 
it currently is.  Unfortunately, that seems like it will be a long long 
time.

	-hpa



  reply	other threads:[~2002-01-06 21:09 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 [this message]
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
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=3C38BCE6.3030302@zytor.com \
    --to=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.