lkml.org 
[lkml]   [2004]   [Aug]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH 1/3] [Generic] Transition /proc/cpuinfo -> sysfs

- Add printk to cpuinfo_open reminding user to transition to sysfs
- Add arch_cpuinfo field to struct cpu

diff -Nru a/fs/proc/proc_misc.c b/fs/proc/proc_misc.c
--- a/fs/proc/proc_misc.c Wed Aug 11 14:46:15 2004
+++ b/fs/proc/proc_misc.c Wed Aug 11 14:46:15 2004
@@ -258,11 +258,18 @@
return proc_calc_metrics(page, start, off, count, eof, len);
}

+#define CPUINFO_REMOVAL_DATE "September 1st, 2005"
extern struct seq_operations cpuinfo_op;
static int cpuinfo_open(struct inode *inode, struct file *file)
{
+ printk(KERN_WARNING "Using depecrated /proc/cpuinfo interface\n");
+ printk(KERN_WARNING "This interface will be deleted on %s\n",
+ CPUINFO_REMOVAL_DATE);
+ printk(KERN_WARNING "Please use syfs interface instead\n");
+
return seq_open(file, &cpuinfo_op);
}
+
static struct file_operations proc_cpuinfo_operations = {
.open = cpuinfo_open,
.read = seq_read,
diff -Nru a/include/linux/cpu.h b/include/linux/cpu.h
--- a/include/linux/cpu.h Wed Aug 11 14:46:15 2004
+++ b/include/linux/cpu.h Wed Aug 11 14:46:15 2004
@@ -28,6 +28,7 @@
struct cpu {
int node_id; /* The node which contains the CPU */
int no_control; /* Should the sysfs control file be created? */
+ void *arch_cpuinfo; /* Per-cpu arch data */
struct sys_device sysdev;
};

--
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/

"Unlike me, many of you have accepted the situation of your imprisonment and
will die here like rotten cabbages." - Number 6
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.083 / U:3.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site