[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1655f5dc49ab77f94e350ecbdc93e8d9b31acf61.1680058548.git.wuzongyong@linux.alibaba.com>
Date: Wed, 29 Mar 2023 10:59:37 +0800
From: Wu Zongyong <wuzongyong@...ux.alibaba.com>
To: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, linux-kernel@...r.kernel.org
Cc: Wu Zongyong <wuzongyong@...ux.alibaba.com>,
thomas.lendacky@....com, tony.luck@...el.com,
kirill.shutemov@...ux.intel.com, wutu.xq2@...ux.alibaba.com
Subject: [RFC PATCH] x86/insn: support decode MOVSXD instruction for MMIO
It seems MOVSXD which opcode is 0x63 is not handled, support
to decode it in insn_decode_mmio().
Signed-off-by: Wu Zongyong <wuzongyong@...ux.alibaba.com>
---
arch/x86/lib/insn-eval.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/x86/lib/insn-eval.c b/arch/x86/lib/insn-eval.c
index 558a605929db..db6f93bad219 100644
--- a/arch/x86/lib/insn-eval.c
+++ b/arch/x86/lib/insn-eval.c
@@ -1607,6 +1607,10 @@ enum insn_mmio_type insn_decode_mmio(struct insn *insn, int *bytes)
return INSN_MMIO_DECODE_FAILED;
switch (insn->opcode.bytes[0]) {
+ case 0x63: /* MOVSXD r64, m32 */
+ *bytes = 4;
+ type = INSN_MMIO_READ_SIGN_EXTEND;
+ break;
case 0x88: /* MOV m8,r8 */
*bytes = 1;
fallthrough;
--
2.34.3
Powered by blists - more mailing lists