From: Daniel Egger <degger@fhm.edu>
To: Juan Quintela <quintela@mandrakesoft.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Why does C3 CPU downgrade in kernel 2.4.20?
Date: 10 Dec 2002 16:40:42 +0100 [thread overview]
Message-ID: <1039534841.31316.33.camel@sonja> (raw)
In-Reply-To: <m27kei9hd3.fsf@demo.mitica>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
Am Die, 2002-12-10 um 13.40 schrieb Juan Quintela:
> Have you tested it?
Sort of.... :/
> Here, we got cmov to work if the two operands are registers, if any of
> the operands is in memory, it don't work.
Now *this* is really informative because it explains why my
testapplication which uses
80488c7: 0f 43 d0 cmovae %eax,%edx
doesn't SEGILL.
> Been there, been burned :p
Me too, just this morning.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-12-10 15:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 4:02 Why does C3 CPU downgrade in kernel 2.4.20? Joseph
2002-12-10 5:52 ` Dave Jones
2002-12-10 7:22 ` Daniel Egger
2002-12-10 7:24 ` Dave Jones
2002-12-10 7:53 ` Daniel Egger
2002-12-10 12:40 ` Juan Quintela
2002-12-10 15:40 ` Daniel Egger [this message]
2002-12-10 16:51 ` Alan Cox
2002-12-10 19:39 ` Daniel Egger
2002-12-10 20:17 ` Jeff Garzik
2002-12-10 21:24 ` Alan Cox
2002-12-11 18:51 ` Bill Davidsen
2002-12-11 19:14 ` Dave Jones
2002-12-11 19:42 ` Jeff Garzik
2002-12-11 19:51 ` Joel Jaeggli
2002-12-12 9:17 ` Joseph
2002-12-12 13:33 ` Dave Jones
2002-12-13 6:55 ` Joseph
2002-12-13 11:04 ` Daniel Egger
2002-12-13 11:57 ` Dave Jones
2002-12-11 21:00 ` Alan Cox
2002-12-12 10:19 ` P
2002-12-11 13:19 ` Denis Vlasenko
2002-12-11 10:58 ` Dave Jones
2002-12-11 19:09 ` Denis Vlasenko
2002-12-11 14:59 ` Dave Jones
2002-12-12 18:09 ` Pavel Machek
2002-12-14 16:46 ` Denis Vlasenko
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=1039534841.31316.33.camel@sonja \
--to=degger@fhm.edu \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.