XED commit 1b2fd94425 ("Update MOVSXD to modern behavior") points out
that as of SDM rev 064 MOVSXD is specified to read only 16 bits from
memory (or register) when used without REX.W and with operand size
override. Since the upper 16 bits of the value read won't be used
anyway in this case, make the emulation uniformly follow this more
compatible behavior when not emulating an AMD-like CPU, at the risk
of missing an exception when emulating on/for older hardware (the
boundary at SandyBridge noted in said commit looks questionable - I've
observed the "new" behavior also on Westmere).
While touching this code I also noticed that #UD outside of protected
mode gets raised for ARPL only after having read the memory operand -
correct this atthe same time by moving up the respective construct.
Signed-off-by: Jan Beulich <jbeul...@suse.com>
--- a/xen/arch/x86/x86_emulate/x86_emulate.c
+++ b/xen/arch/x86/x86_emulate/x86_emulate.c
@@ -4048,8 +4048,12 @@ x86_emulate(
/* movsxd */
if ( ea.type == OP_REG )
src.val = *ea.reg;
- else if ( (rc = read_ulong(ea.mem.seg, ea.mem.off,
- &src.val, 4, ctxt, ops)) )
+ else if ( (rc = read_ulong(ea.mem.seg, ea.mem.off, &src.val,
+ (op_bytes == 2 &&
+ !(ctxt->cpuid->x86_vendor &
+ (X86_VENDOR_AMD | X86_VENDOR_HYGON))
+ ? 2 : 4),
+ ctxt, ops)) )
goto done;
dst.val = (int32_t)src.val;
}
@@ -4058,6 +4062,8 @@ x86_emulate(
/* arpl */
unsigned int src_rpl = dst.val & 3;
+ generate_exception_if(!in_protmode(ctxt, ops), EXC_UD);
+
dst = ea;
dst.bytes = 2;
if ( dst.type == OP_REG )
@@ -4075,7 +4081,6 @@ x86_emulate(
_regs.eflags &= ~X86_EFLAGS_ZF;
dst.type = OP_NONE;
}
- generate_exception_if(!in_protmode(ctxt, ops), EXC_UD);
}
break;
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
