mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][2.6.0-test3] i386 cpuid.c devfs support 2/2
Date: Sun, 10 Aug 2003 12:52:26 +0400	[thread overview]
Message-ID: <200308101252.26584.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 104 bytes --]

the same question about default permissions as for msr.c; the same problem 
with module unload.

-andrey

[-- Attachment #2: 2.6.0-test3-cpuid_devfs.patch --]
[-- Type: text/x-diff, Size: 957 bytes --]

--- linux-2.6.0-test3-smp/arch/i386/kernel/cpuid.c.devfs	2003-05-05 03:52:48.000000000 +0400
+++ linux-2.6.0-test3-smp/arch/i386/kernel/cpuid.c	2003-08-09 22:30:39.000000000 +0400
@@ -39,6 +39,8 @@
 #include <linux/smp_lock.h>
 #include <linux/fs.h>
 
+#include <linux/devfs_fs_kernel.h>
+
 #include <asm/processor.h>
 #include <asm/msr.h>
 #include <asm/uaccess.h>
@@ -156,17 +158,27 @@ static struct file_operations cpuid_fops
 
 int __init cpuid_init(void)
 {
+  int i;
+
   if (register_chrdev(CPUID_MAJOR, "cpu/cpuid", &cpuid_fops)) {
     printk(KERN_ERR "cpuid: unable to get major %d for cpuid\n",
 	   CPUID_MAJOR);
     return -EBUSY;
   }
 
+  for (i = 0; i < NR_CPUS; i++)
+    devfs_mk_cdev(MKDEV(CPUID_MAJOR, i), S_IFCHR | S_IRUGO, "cpu/%d/cpuid", i);
+
   return 0;
 }
 
 void __exit cpuid_exit(void)
 {
+  int i;
+
+  for (i = 0; i < NR_CPUS; i++)
+    devfs_remove("cpu/%d/cpuid", i);
+
   unregister_chrdev(CPUID_MAJOR, "cpu/cpuid");
 }
 

             reply	other threads:[~2003-08-10  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  8:52 Andrey Borzenkov [this message]
2003-08-10 13:59 ` Dave Jones
2003-08-10 14:14   ` Andrey Borzenkov

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=200308101252.26584.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --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

all inboxes | Powered by JetHome®