From: Ronald Wahl <Ronald.Wahl@informatik.tu-chemnitz.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [Q] Looking for an emulation for CMOV* instructions.
Date: 16 Jan 2002 18:48:49 +0100 [thread overview]
Message-ID: <m21ygquqym.fsf@goliath.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.1020116110901.13296A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1020116110901.13296A-100000@chaos.analogic.com>
On Wed, 16 Jan 2002 11:16:55 -0500 (EST), Richard B Johnson wrote:
> On Wed, 16 Jan 2002, Jamie Lokier wrote:
>> Alan Cox wrote:
>> > > What's the point of optimizing an IF to a cmov if I have
>> > > to insert another IF to see if I can use cmov?
>> >
>> > I've always wondered. Intel made the instruction optional yet there isnt
>> > an obvious way to do runtime fixups on it
>>
>> Yes there is -- emulation! :-)
>>
> It's just as bad, probably worse! You trap on an invalid op-code. The
> trap-handler checks the op-code and if it's emulated, it emulates it
> and returns to the executing task. This takes many instruction cycles,
> certainly more than `if(cmov) doit; else do_something_else;` --which,
> itself, takes many more instruction cycles than cmov is supposed to
> reduce. It's a no-win situation. The only way to win is a compile-time
> choice. This means customizing for your CPU IFF it has the cmov
> instruction.
It is a big win in the situation where you have only a binary for i686
and want or better must execute it e.g. on a i586. This was the reason
why I asked initially.
ron
--
/\/\ Dipl.-Inf. Ronald Wahl /\/\ C S N /\/\
\/\/ ronald.wahl@informatik.tu-chemnitz.de \/\/ ------------------ \/\/
/\/\ http://www.tu-chemnitz.de/~row/ /\/\ network and system /\/\
\/\/ GnuPG/PGP key available \/\/ administration \/\/
next prev parent reply other threads:[~2002-01-16 17:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 23:08 Ronald Wahl
2002-01-10 23:28 ` Alan Cox
2002-01-11 0:08 ` Ronald Wahl
2002-01-11 0:26 ` Alan Cox
2002-01-11 0:39 ` Ronald Wahl
2002-01-11 0:54 ` Alan Cox
2002-01-11 1:09 ` Martin Eriksson
2002-01-11 1:42 ` Timothy Covell
2002-01-11 2:16 ` Alan Cox
2002-01-11 18:24 ` Ronald Wahl
2002-01-11 22:18 ` Richard Henderson
2002-01-11 23:07 ` Alan Cox
2002-01-11 23:26 ` Albert D. Cahalan
2002-01-11 23:40 ` Alan Cox
2002-01-16 15:18 ` Jamie Lokier
2002-01-16 16:16 ` Richard B. Johnson
2002-01-16 17:48 ` Ronald Wahl [this message]
2002-01-16 17:30 ` Dave Jones
2002-01-17 11:54 ` Maciej W. Rozycki
2002-01-11 19:59 ` Hans-Peter Jansen
2002-01-11 20:05 ` Ronald Wahl
2002-01-11 23:19 ` Alan Cox
2002-01-12 6:27 ` Pavel Machek
2002-04-12 20:48 ` H. Peter Anvin
2002-01-12 6:34 ` Pavel Machek
2002-01-18 17:38 ` David Woodhouse
2002-01-18 22:01 ` Pavel Machek
2002-01-11 23:25 ` Alistair Riddell
[not found] <fa.eln67tv.a4io16@ifi.uio.no>
[not found] ` <fa.gp0gofv.1p4se16@ifi.uio.no>
2002-01-11 8:12 ` Giacomo Catenazzi
2002-01-11 9:25 willy tarreau
2002-01-11 17:55 ` Ronald Wahl
[not found] <m26669olcu.fsf@goliath.csn.tu-chemnitz.de.suse.lists.linux.kernel>
[not found] ` <E16Oocq-0005tX-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-01-11 9:54 ` Andi Kleen
2002-01-12 6:31 ` Pavel Machek
2002-01-12 7:52 ` H. Peter Anvin
[not found] <200201111845.g0BIjS2318104@saturn.cs.uml.edu>
2002-01-12 9:00 ` willy tarreau
2002-01-12 18:57 ` Alan Cox
2002-01-12 10:48 Adam J. Richter
2002-01-12 11:25 ` David Weinehall
2002-01-12 13:18 ` Brian Gerst
2002-01-12 20:43 ` H. Peter Anvin
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=m21ygquqym.fsf@goliath.csn.tu-chemnitz.de \
--to=ronald.wahl@informatik.tu-chemnitz.de \
--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
all inboxes | Powered by JetHome®