From: Michel LESPINASSE <walken@zoy.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test11-pre5 breaks vmware
Date: Wed, 15 Nov 2000 12:49:32 -0800 [thread overview]
Message-ID: <20001115124931.B28499@windriver.com> (raw)
In-Reply-To: <CF021B54DF0@vcnet.vc.cvut.cz> <Pine.LNX.4.21.0011151454590.10690-100000@godzilla.spiteful.org> <8uuqmv$el4$1@cesium.transmeta.com>
In-Reply-To: <8uuqmv$el4$1@cesium.transmeta.com>; from hpa@zytor.com on Wed, Nov 15, 2000 at 12:12:15PM -0800
On Wed, Nov 15, 2000 at 12:12:15PM -0800, 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.
Is it also OK to use the cpuid opcode in userspace ? (after checking
for its presence with the 0x200000 eflags bit)
--
Michel "Walken" LESPINASSE
Of course I think I'm right. If I thought I was wrong, I'd change my mind.
-
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 prev parent reply other threads:[~2000-11-15 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 17:47 test11-pre5 breaks vmware Petr Vandrovec
2000-11-15 20:05 ` Scott Murray
2000-11-15 20:12 ` H. Peter Anvin
2000-11-15 20:49 ` Michel LESPINASSE [this message]
2000-11-15 20:50 ` H. Peter Anvin
2000-11-16 0:29 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 22:39 Petr Vandrovec
2000-11-15 17:57 Petr Vandrovec
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=20001115124931.B28499@windriver.com \
--to=walken@zoy.org \
--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