Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Wu Zongyong <wuzongyong@linux.alibaba.com>
To:     tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com,
        x86@kernel.org, linux-kernel@vger.kernel.org
Cc:     Wu Zongyong <wuzongyong@linux.alibaba.com>,
        thomas.lendacky@amd.com, tony.luck@intel.com,
        kirill.shutemov@linux.intel.com, wutu.xq2@linux.alibaba.com
Subject: [RFC PATCH] x86/insn: support decode MOVSXD instruction for MMIO
Date:   Wed, 29 Mar 2023 10:59:37 +0800
Message-Id: <1655f5dc49ab77f94e350ecbdc93e8d9b31acf61.1680058548.git.wuzongyong@linux.alibaba.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

It seems MOVSXD which opcode is 0x63 is not handled, support
to decode it in insn_decode_mmio().

Signed-off-by: Wu Zongyong <wuzongyong@linux.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