From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: AMD64: 64 bit kernel 32 bit userland - some pending questions
Date: Tue, 6 Jun 2006 21:08:26 -0700 (PDT) [thread overview]
Message-ID: <e65jfq$m6v$1@terminus.zytor.com> (raw)
In-Reply-To: 787b0d920606062011j21083e80v659228a7565ecfab@mail.gmail.com
Followup to: <787b0d920606062011j21083e80v659228a7565ecfab@mail.gmail.com>
By author: "Albert Cahalan" <acahalan@gmail.com>
In newsgroup: linux.dev.kernel
>
> The bigger problem is that 32-bit code has fewer CPU registers.
> (nobody has done an ILP32 ABI for long mode) This is slow.
>
The issue isn't the ABI, the issue is that the processor doesn't
support it, since some of the opcodes mean different things in 16-,
32- and 64-bit mode. The opcodes which access the high half of the
register sets (REX prefixes) in 64-bit mode are INC and DEC
instructions in 16- and 32-bit mode.
AMD was apparently considering adding a "REX32" mode at some point,
but rather predictably noone was interested enough to make it
worthwhile.
-hpa
next prev parent reply other threads:[~2006-06-07 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 3:11 AMD64: 64 bit kernel 32 bit userland - some pending questions Albert Cahalan
2006-06-07 4:08 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 9:34 Thomas Glanzmann
2006-06-06 10:42 ` Andi Kleen
2006-06-06 10:49 ` Thomas Glanzmann
2006-06-06 11:51 ` Rafael J. Wysocki
2006-06-06 11:55 ` Andi Kleen
2006-06-06 11:56 ` Marcus Meissner
2006-06-06 12:11 ` Rafael J. Wysocki
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='e65jfq$m6v$1@terminus.zytor.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 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.