public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: transmeta cpu code question
Date: 23 Nov 2003 22:54:54 -0800	[thread overview]
Message-ID: <bps9vu$osu$1@cesium.transmeta.com> (raw)
In-Reply-To: 20031121084857.GA10343@mail.shareable.org

Followup to:  <20031121084857.GA10343@mail.shareable.org>
By author:    Jamie Lokier <jamie@shareable.org>
In newsgroup: linux.dev.kernel
> 
> What would be the point in that?  Surely the CMS overhead for decoding
> the rarely used x86 instructions is negligable, precisely because of
> their rarity?
> 

Pretty much.

The bulk of the time spent in CMS is in the backend scheduler, at
which time the original x86 instructions are pretty much
unrecognizable.

If there is something that one could imagine doing at the CMS level to
help on Linux, it would probably be something like making it optional
to actually perform stores beneath the stack pointer, in which case a
lot of stack frame operations could be done purely in registers.  CMS
will do them in registers already, but will be forced to perform a
store at the end of the translation anyway in order to keep exact x86
semantics.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

  reply	other threads:[~2003-11-24  6:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  2:02 transmeta cpu code question Nico Schottelius
2003-11-20  2:10 ` Ben Hoskings
2003-11-20  8:38   ` Nico Schottelius
2003-11-20 17:33     ` H. Peter Anvin
2003-11-20 23:25       ` Jamie Lokier
2003-11-21  8:34         ` John Bradford
2003-11-21  8:48           ` Jamie Lokier
2003-11-24  6:54             ` H. Peter Anvin [this message]
2003-11-24 13:19               ` Jamie Lokier
2003-11-20  2:53 ` Ben Collins
2003-11-20  3:06   ` Kevin P. Fleming
2003-11-20 13:25     ` Ben Collins
2003-11-20  3:18   ` Ben Hoskings
2003-11-20  6:57   ` Eric Sandall

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='bps9vu$osu$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