[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230331022414.GB435@L-PF27918B-1352.localdomain>
Date: Fri, 31 Mar 2023 10:24:14 +0800
From: Wu Zongyong <wuzongyong@...ux.alibaba.com>
To: kirill.shutemov@...ux.intel.com
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, linux-kernel@...r.kernel.org,
thomas.lendacky@....com, tony.luck@...el.com,
wutu.xq2@...ux.alibaba.com
Subject: Re: [RFC PATCH] x86/insn: support decode MOVSXD instruction for MMIO
On Thu, Mar 30, 2023 at 03:39:51PM +0300, kirill.shutemov@...ux.intel.com wrote:
> On Wed, Mar 29, 2023 at 10:59:37AM +0800, Wu Zongyong wrote:
> > It seems MOVSXD which opcode is 0x63 is not handled, support
> > to decode it in insn_decode_mmio().
>
> Do you have a particular user in mind?
To be honest, I don't find a specific user which uses the MOVSXD.
But both Intel and AMD's instructions reference contains MOVSXD and lots
of MOVSXD instructions occur when I "objdump -S vmlinux", so I think it
may be useful to support it in insn_decode_mmio().
Are there some special consideration about this instruction?
>
> --
> Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists