From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Microsecond accuracy
Date: 7 Dec 2000 07:33:23 -0800 [thread overview]
Message-ID: <90oak3$326$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012071233420.970-100000@penguin.homenet> <Pine.LNX.4.21.0012071411170.970-100000@penguin.homenet>
Followup to: <Pine.LNX.4.21.0012071411170.970-100000@penguin.homenet>
By author: Tigran Aivazian <tigran@veritas.com>
In newsgroup: linux.dev.kernel
>
> while we are on this subject, please let me emphasize that you should
> _not_ be using cpuid instruction to detect the presence of TSC but should
> parse the /proc/cpuinfo file. There are many valid reasons why Linux's
> idea of TSC presence may not be the same as hardware's (cpuid
> instruction) idea.
>
Unfortunately the most important instance of the in-kernel flag -- the
global one in the somewhat misnamed boot_cpu_data.x86_features --
isn't actually readable in the /proc/cpuinfo file. It is perfectly
possible (e.g. the "notsc" option) for ALL the CPUs to report this
capability, but the global capability to still be off.
I would like to have exported the global capabilities into
/proc/cpuinfo, but I'm worried about breaking software (the "flags"
versus "features" issue was bad enough -- unfortunately, in cases like
this, there probably is no "good" solution.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-12-07 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 11:42 Microsecond accuracy Kotsovinos Vangelis
2000-12-07 12:36 ` Tigran Aivazian
2000-12-07 14:13 ` Tigran Aivazian
2000-12-07 15:33 ` H. Peter Anvin [this message]
2000-12-07 16:07 ` Maciej W. Rozycki
2000-12-07 19:28 ` [PATCH] setup.c notsc " Hugh Dickins
2000-12-07 20:48 ` Maciej W. Rozycki
2000-12-13 14:10 ` H. Peter Anvin
2000-12-07 16:54 ` Christopher Friesen
2000-12-08 0:17 ` Kotsovinos Vangelis
2000-12-07 21:14 ` Karim Yaghmour
2000-12-08 0:18 ` Kotsovinos Vangelis
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='90oak3$326$1@cesium.transmeta.com' \
--to=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