From mboxrd@z Thu Jan 1 00:00:00 1970
From: "Jason Thomas"
Subject: x86 versus 64 bit emulation complexity
Date: Mon, 14 Nov 2011 14:46:25 -0800
Message-ID: <007501cca31f$3e4b55e0$bae201a0$@com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1163047647=="
Return-path:
Content-Language: en-us
List-Unsubscribe: ,
List-Post:
List-Help:
List-Subscribe: ,
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org
This is a multi-part message in MIME format.
--===============1163047647==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0076_01CCA2DC.302815E0"
Content-Language: en-us
This is a multi-part message in MIME format.
------=_NextPart_000_0076_01CCA2DC.302815E0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
This is a general question about the complexity of emulating a 32 bit x86
environment compared to a 64 bit environment. What are the differences
between the two types. Does one require much more code/complexity to emulate
compared with the other?
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
------=_NextPart_000_0076_01CCA2DC.302815E0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
This is a genera=
l question about the complexity of emulating a 32 bit x86 environment compa=
red to a 64 bit environment. What are the differences between the two types=
. Does one require much more code/complexity to emulate compared with the o=
ther?
CONFIDENTIALIT=
Y
NOTICE:This e-mail message, including any attachments, is for the =
sole use of the intended recipient(s) and may contain confidential and priv=
ileged information. Any unauthorized review, use, disclosure or distributio=
n is prohibited. If you are not the intended recipient, please contact the =
sender by reply e-mail and destroy all copies of the original message.