From: "Jason Thomas" <jthomas@islinc.com>
To: xen-devel@lists.xensource.com
Subject: x86 versus 64 bit emulation complexity
Date: Mon, 14 Nov 2011 14:46:25 -0800 [thread overview]
Message-ID: <007501cca31f$3e4b55e0$bae201a0$@com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2365 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-11-14 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 22:46 Jason Thomas [this message]
2011-11-15 1:43 ` x86 versus 64 bit emulation complexity Jeremy Fitzhardinge
2011-11-15 2:17 ` Todd Deshane
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='007501cca31f$3e4b55e0$bae201a0$@com' \
--to=jthomas@islinc.com \
--cc=xen-devel@lists.xensource.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.