From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test11-pre5 breaks vmware
Date: Wed, 15 Nov 2000 22:39:23 MET-1 [thread overview]
Message-ID: <CF5004B75B8@vcnet.vc.cvut.cz> (raw)
On 15 Nov 00 at 12:12, H. Peter Anvin wrote:
> Also, if a piece of software needs raw CPUID information (unlike the
> "cooked" one provided by recent kernels) it should use
> /dev/cpu/*/cpuid.
There are two problems, first breaking procfs field name for no good reason
(you can name x86 features as 'flags' and amd/cyrix/...
as you named... There is certainly fewer apps which search 'flags'
for AMD feature than apps which search 'flags' for x86 feature;
you can also emulate old flags field by merging all features together,
but I'm not asking for this).
Second problem is that I know no system which has /dev/cpu/*/* file.
Maybe it is just my problem...
But if you could modify cpuid/msr registration interface so that they'll
appear on my /devfs, it would be much nicer. Currently there is only
'microcode' and 'mtrr' in /devfs/cpu, and no 0,1 subdirectories...
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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-11-15 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 22:39 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 17:57 test11-pre5 breaks vmware Petr Vandrovec
2000-11-15 17:47 Petr Vandrovec
2000-11-15 20:05 ` Scott Murray
2000-11-15 20:12 ` H. Peter Anvin
2000-11-15 20:49 ` Michel LESPINASSE
2000-11-15 20:50 ` H. Peter Anvin
2000-11-16 0:29 ` Albert D. Cahalan
2000-11-14 12:47 More modutils: It's probably worse Petr Vandrovec
2000-11-15 1:59 ` test11-pre5 breaks vmware Tigran Aivazian
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=CF5004B75B8@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=hpa@zytor.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