From: Deepak Saxena <dsaxena@plexity.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, greg@kroah.com
Subject: [PATCH 0/3] Transition /proc/cpuinfo -> sysfs
Date: Wed, 11 Aug 2004 15:41:17 -0700 [thread overview]
Message-ID: <20040811224117.GA6450@plexity.net> (raw)
Following this email will be a set of patches that provide a first pass
at exporting information currently in /proc/cpuinfo to sysfs for i386 and
ARM. There are applications that are dependent on /proc/cpuinfo atm, so we
can't just kill it, but we should agree on a kill date and require all
arches & apps to transition by that point. I've added code to
proc_misc.c to remind the user that the cpuinfo interface is going
away (currently using arbitrary date ~1 year from now). I've also
added a pointer to struct cpu that can be used by arch code to
store any information that might be needed during attribute printing.
Couple of questions:
- Do we want to standardize on a set of attributes that all CPUs
must provide to sysfs? bogomips, L1 cache size/type/sets/assoc (when
available), L2 cache (L3..L4), etc? This would make the output be the
same across architectures for those features and would simply require
adding some fields to struct cpu to carry this data and some generic
ATTR entries to drivers/base/cpu.c. I am all for standardized
interfaces so I'll do a first pass at this if desired.
- On an HT setup, do we want link(s) pointing to sibling(s)?
- Currently the bug and feature fields on x86 have "yes" and "no".
Do we want the same in sysfs or 1|0?
- Instead of dumping the "flags" field, should we just dump cpu
registers as hex strings and let the user decode (as the comment
for the x86_cap_flags implies.
I'll try to do MIPS, SH, and PPC when I get a chance (all I have access
to), but have other things to do for a while, so want comments on above
questions first.
Tnx,
~Deepak
--
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
next reply other threads:[~2004-08-11 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 22:41 Deepak Saxena [this message]
2004-08-11 22:42 ` [PATCH 1/3] [Generic] Transition /proc/cpuinfo -> sysfs Deepak Saxena
2004-08-11 22:44 ` [PATCH 2/3] [i386] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 3/3] [ARM] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 0/3] " Deepak Saxena
2004-08-11 23:13 ` Dave Jones
2004-08-11 23:42 ` Deepak Saxena
2004-08-11 23:59 ` Dave Jones
2004-08-12 2:45 ` Deepak Saxena
2004-08-12 11:07 ` Dave Jones
2004-08-15 6:11 ` Andrew Morton
2004-08-15 6:33 ` Greg KH
2004-08-12 5:03 ` Lamont R. Peterson
2004-08-12 10:56 ` Dave Jones
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=20040811224117.GA6450@plexity.net \
--to=dsaxena@plexity.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--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