From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Alan J . Wylie" <alan@wylie.me.uk>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: [PATCH] x86: XOP prefix instructions decoder support
Date: Wed, 20 Aug 2025 10:00:04 +0900 [thread overview]
Message-ID: <20250820100004.15a49b907b334e821f0a0e73@kernel.org> (raw)
In-Reply-To: <F5D549B0-F8F7-467A-8F8D-7ED5EE4369D3@zytor.com>
On Sat, 16 Aug 2025 18:36:17 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> The easiest way to think of XOP is as a VEX3 supporting a different set of map numbers (VEX3 supports maps 0-31, XOP maps are 8-31 but separate); however, the encoding format is the same.
Hmm, OK. We need to enable VEX3 support too. What about the opcode?
Most of the opcode are the same, or different instructions?
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-08-20 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 7:46 Masami Hiramatsu (Google)
2025-08-17 0:32 ` Masami Hiramatsu
2025-08-17 1:36 ` H. Peter Anvin
2025-08-20 1:00 ` Masami Hiramatsu [this message]
2025-08-20 15:04 ` H. Peter Anvin
2025-08-17 10:47 ` Alan J. Wylie
2025-08-20 1:02 ` Masami Hiramatsu
2025-08-18 15:25 ` [tip: x86/misc] x86/insn: Add " tip-bot2 for Masami Hiramatsu (Google)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250820100004.15a49b907b334e821f0a0e73@kernel.org \
--to=mhiramat@kernel.org \
--cc=alan@wylie.me.uk \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®