From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7BE7C1A76D4; Wed, 20 Aug 2025 01:00:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755651609; cv=none; b=U2fYrqrKgnO2ycV2rSCrLU9+Tiwlexzx36/JFndseRvWgdZqx5Fh9qsZvOvEQdkNiWfxYhX1443lMOWmnaj2W4Y4jZ9Y50a7veYAWvrrfLeZl4Un60ANMQz92w1hhElZsEmyWD76PfmL6LinbaveBJtbAsra4ZrUer0oeXH8hvw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755651609; c=relaxed/simple; bh=JFhoL3YfNHgdhhfjYUv35Lds5sUeHFBImU5hZ4572/w=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=FuXUvzwakNjTDICrCXeGUgngYFs4QQk3vrHfTywiCLxHrcJIsYS0Bxp6JiKT6V7YkDUJ76ifI3SB0NWD1CJXr0yauWrhjapzRcZ55BnNoQrlQT8C5FriiPwj5e8rB10L+yRdE9s/pigvpmG1kLQg6ZEwv2oI7kzjJW5EtOe/rO0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=lUVboWDQ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="lUVboWDQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83657C113D0; Wed, 20 Aug 2025 01:00:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1755651609; bh=JFhoL3YfNHgdhhfjYUv35Lds5sUeHFBImU5hZ4572/w=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=lUVboWDQQa5eQ8NCFUg1I7VBbMv+kM19AHe9O3teKGDILXKFdyIkPkL5ybQYv8Slv ytP4dyhynjC80KpfDHTCzlifsUXIS+PM7ySIRicNLi/ReoypznSfyvVw96KAr0mXXD RkyNfEZ+UCVenHI05I7h2Zc8NBjXTNt1R9YJX3e2IeXstEdE2C6moiwbXu+W9++/KJ zsGszwA9Hx1Dmzy4Qy++ORISXNGXJiqVARw9PyUqU1XbvIqnI5Qp25grSN1d2GH303 LuUXVVMUnvtVNuZCS/1/8gho0B8VQF6TBCTzMW2E1pFwLpU9y2otsq/D+hTtZe2ZlM K14j2y9brapAQ== Date: Wed, 20 Aug 2025 10:00:04 +0900 From: Masami Hiramatsu (Google) To: "H. Peter Anvin" Cc: "Alan J . Wylie" , Josh Poimboeuf , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , linux-kernel@vger.kernel.org, regressions@lists.linux.dev, stable@vger.kernel.org, Linus Torvalds , x86@kernel.org Subject: Re: [PATCH] x86: XOP prefix instructions decoder support Message-Id: <20250820100004.15a49b907b334e821f0a0e73@kernel.org> In-Reply-To: References: <175386161199.564247.597496379413236944.stgit@devnote2> <20250817093240.527825424989e5e2337b5775@kernel.org> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 16 Aug 2025 18:36:17 -0700 "H. Peter Anvin" 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)