From: ryan <ryan@javien.com>
To: linux-kernel@vger.kernel.org
Subject: Change of /proc/cpuinfo format
Date: Tue, 05 Dec 2000 15:06:45 -0800 [thread overview]
Message-ID: <3A2D7505.2BB48C48@javien.com> (raw)
Hi,
There was a minor change to the format of /proc/cpuinfo which hoses
several programs. Most notably is vmware.
The details are the field formerly known as 'flags' is now known as
'features' which breaks any programs attempting to parse /proc/cpuinfo
and making decisions about what feature set the cpu supports.
I'm not quite sure why the name change is necessary, and even if one
wants to keep the name change there is a discontunity of cpuinfo formats
and programs which intend to run on kernels 2.2 and 2.4 needs to know
this...
Here is a small patch to save your typing fingers:
--- setup.c.old Tue Dec 5 15:01:21 2000
+++ setup.c Tue Dec 5 14:53:52 2000
@@ -2131,7 +2131,7 @@
"fpu_exception\t: %s\n"
"cpuid level\t: %d\n"
"wp\t\t: %s\n"
- "features\t:",
+ "flags\t:",
c->fdiv_bug ? "yes" : "no",
c->hlt_works_ok ? "no" : "yes",
c->f00f_bug ? "yes" : "no",
in linux/arch/i386/kernel
-ryan
--
Ryan Rawson
Software Designer
ryan@javien.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-05 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 23:06 ryan [this message]
2000-12-05 23:21 ` Change of /proc/cpuinfo format Peter Samuelson
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=3A2D7505.2BB48C48@javien.com \
--to=ryan@javien.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;
as well as URLs for NNTP newsgroup(s).