From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Jordan <ledzep37@home.com>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Error in x86 CPU capabilities starting with test5/6
Date: Fri, 17 Nov 2000 13:04:18 +0100 [thread overview]
Message-ID: <20001117130418.B3572@gruyere.muc.suse.de> (raw)
In-Reply-To: <3A14FF48.E554BE1B@home.com> <14869.6415.500026.432150@harpo.it.uu.se>
In-Reply-To: <14869.6415.500026.432150@harpo.it.uu.se>; from mikpe@csd.uu.se on Fri, Nov 17, 2000 at 12:39:59PM +0100
On Fri, Nov 17, 2000 at 12:39:59PM +0100, Mikael Pettersson wrote:
> Jordan writes:
> > I have been running a plug in for xmms for some time that uses the
> > aviplay program and avifile library...then when upgrading to test5/6 I
> > start getting this error message when running xmms:
> >
> > ERROR: no time-stamp counter found! Quitting.
> > ...
> > contents of /proc/cpuinfo:
> > ...
> > features : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
>
> The 'flags' line in /proc/cpuinfo was recently renamed 'features', due to
> some semantic changes. You have a user-space program which parses /proc/cpuinfo
> instead of executing CPUID itself, so it breaks.
The program would be broken if it executed CPUID itself, because it has no way to guarantee
that the CPUID is executed on all CPUs the scheduler may later move the task too.
I think it is also nasty to break non broken programs this way, looking for
flags in /proc/cpuinfo is the only reliable way to do the checks on 2.2.
-Andi (proud owner of an AMP system with one CPU implementing FXSR and one not,
which causes lots of interesting problems)
-
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-17 12:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 9:50 Jordan
2000-11-17 11:39 ` Mikael Pettersson
2000-11-17 11:58 ` Tigran Aivazian
2000-11-17 12:10 ` Alan Cox
2000-11-17 12:51 ` Christoph Rohland
2000-11-17 13:08 ` Jeff Garzik
2000-11-17 13:21 ` Christoph Rohland
2000-11-17 13:31 ` Andi Kleen
2000-11-17 13:40 ` Jeff Garzik
2000-11-17 13:54 ` Andi Kleen
2000-11-17 14:02 ` Tigran Aivazian
2000-11-17 14:30 ` Christoph Rohland
2000-11-17 14:50 ` Alan Cox
2000-11-17 14:00 ` Arjan van de Ven
2000-11-17 15:18 ` Andrea Arcangeli
2000-11-17 16:06 ` Christoph Rohland
2000-11-17 18:28 ` Andrea Arcangeli
2000-11-18 9:57 ` Christoph Rohland
2000-11-19 10:31 ` Albert D. Cahalan
2000-11-17 13:38 ` Mikael Pettersson
2000-11-17 12:04 ` Andi Kleen [this message]
2000-11-17 12:14 ` Jan Niehusmann
2000-11-17 12:22 ` Andi Kleen
2000-11-17 13:26 ` Mohammad A. Haque
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=20001117130418.B3572@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ledzep37@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®