diff options
author | Keir Fraser <keir.fraser@citrix.com> | 2009-08-19 13:02:04 +0100 |
---|---|---|
committer | Keir Fraser <keir.fraser@citrix.com> | 2009-08-19 13:02:04 +0100 |
commit | b2c296e1c5dcbcca103b5fcc3862de8a3faa99c3 (patch) | |
tree | 84383efb97871a1640b7fc66309724bde6dbf2d9 /tools/tests | |
parent | cf8b52ff53eb09ca463f67067369b22863356c61 (diff) | |
download | xen-b2c296e1c5dcbcca103b5fcc3862de8a3faa99c3.tar.gz xen-b2c296e1c5dcbcca103b5fcc3862de8a3faa99c3.tar.bz2 xen-b2c296e1c5dcbcca103b5fcc3862de8a3faa99c3.zip |
x86-64: adjust emulation of control transfers
While Intel and AMD implementations differ in various respects when
it comes to non-default operand sizes of control transfer instructions
and segment register loads (lfs, lgs, lss), it seems to make senss to
(a) match their behavior if they agree and (b) prefer the more
permissive behavior if they don't agree:
- honor operand size overrides on near brances (AMD does, Intel
doesn't)
- honor operand size overrides on far branches (both Intel and AMD do)
- honor REX.W on far branches (Intel does, AMD doesn't except on far
returns)
- honor REX.W on lfs, lgs, and lss (Intel does, AMD doesn't)
Also, do not permit emulation of pushing/popping segment registers
other than fs and gs as well as that of les and lds (the latter are
particularly important due to the re-use of the respective opcodes as
VEX prefixes in AVX).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Diffstat (limited to 'tools/tests')
0 files changed, 0 insertions, 0 deletions