Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp365980ybb; Wed, 8 Apr 2020 01:07:30 -0700 (PDT) X-Google-Smtp-Source: APiQypJRT7Z7n7O/Hz7+L4uD79vbF+Om0XRrMDoMAe5Jo/SZP8FrWpRkJqOrk3DLmRWFULnciIzX X-Received: by 2002:aca:aa81:: with SMTP id t123mr1556887oie.117.1586333250427; Wed, 08 Apr 2020 01:07:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586333250; cv=none; d=google.com; s=arc-20160816; b=j1ePkhuvnV+ru0jfRtX0SpoDKUR6Ffyadep5FX7JOfxhyiIF6aDu+xSXTNknvCAjHe SmkW5jGhwEZEqfoxsONuiZExQ/KX6ephWa+upTO+K8HJBzRFvuqg1lre14emna6fs/5z XVaeG6d4TRRIbJdQgkg3gzpaVgYeA5wJlyHbCJQu5vkXjTB/MNMStPvecRBAGWfGvmQt xrPGTi4GH5V1a1dGfOQybUNn/gynSoGlfxn3NQS+BafR+9lvvORS8+eGfmErR04C156i JR/waDAzNH0JTLVJ6AyE4YYVw8lzeMCsLXJF79dquWXQnxpnGHzhRJfiugkKy3fJzAju mghA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=rVVhSNwx22ucZl538qVf/mGi/kZi0hY21U0IDhWngTk=; b=lVo0jQ2CYeXoVHcj2LufNtTZaPl1PA7yLKpkoMQ7qhYAGOAUxhYsV0GYHNVi84hK+H g5ulbLAoZ7brrYzYudPbO0r0H43dY0SD3xyQ2zLY7TP6p1huxvk0J9E8eEky4xrZUNrf fCoToMUfAofJM1tDRIRRxl/9q4S2t32TyzF+DJyBErFPUprnfddNu7suOJ6gY5wjZE48 3jXyTVoaysl43YKzWaGNajNREbnuvR8pDVYm8AZGtgiBy8egNjArOHMAjyQ9hayANe8D K9+5fAAIXyiHKKtGbSQs7lLIhC7MX0W5kyVMtdmYB6btqe/MH7q6vkzsIIjw17D2hfL3 Wdqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vgE5cDo9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g1si2411136otn.200.2020.04.08.01.07.16; Wed, 08 Apr 2020 01:07:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vgE5cDo9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726761AbgDHHZp (ORCPT + 99 others); Wed, 8 Apr 2020 03:25:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:48054 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726712AbgDHHZp (ORCPT ); Wed, 8 Apr 2020 03:25:45 -0400 Received: from devnote2 (NE2965lan1.rev.em-net.ne.jp [210.141.244.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6121320730; Wed, 8 Apr 2020 07:25:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586330744; bh=sgM0OgGXdXtnVQaVYMoa5XvNnehXNyhomdt1s63WD7I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=vgE5cDo9x/6xgxvR0n8f1v/TEM6q6/a4gTc5cOOUBQd6Ve7gNd+iABHvAogAc0q4G PLjrumTeHzO0t8H+eGsd2T/ry02ZPsTABVxfugRI3k62xVXKYlw6rXIlzc3JTIMsvt 5aBmrW0vrGsZ2gbta2bmUIw06u4LCDbUDUVgUg9c= Date: Wed, 8 Apr 2020 16:25:36 +0900 From: Masami Hiramatsu To: Masami Hiramatsu Cc: Peter Zijlstra , tglx@linutronix.de, linux-kernel@vger.kernel.org, hch@infradead.org, sean.j.christopherson@intel.com, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org, kenny@panix.com, jeyu@kernel.org, rasmus.villemoes@prevas.dk, pbonzini@redhat.com, fenghua.yu@intel.com, xiaoyao.li@intel.com, nadav.amit@gmail.com, thellstrom@vmware.com, tony.luck@intel.com, rostedt@goodmis.org, gregkh@linuxfoundation.org, jannh@google.com, keescook@chromium.org, David.Laight@aculab.com, dcovelli@vmware.com Subject: Re: [PATCH 3/4] x86,module: Detect VMX vs SLD conflicts Message-Id: <20200408162536.5f14339c3ef5a2b0444d2f06@kernel.org> In-Reply-To: <20200408015124.ec42bcffc1377cb6ea94f785@kernel.org> References: <20200407110236.930134290@infradead.org> <20200407111007.352324393@infradead.org> <20200408015124.ec42bcffc1377cb6ea94f785@kernel.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 Apr 2020 01:51:24 +0900 Masami Hiramatsu wrote: > Hi Peter, > > On Tue, 07 Apr 2020 13:02:39 +0200 > Peter Zijlstra wrote: > > > +static bool insn_is_vmx(struct insn *insn) > > +{ > > + u8 modrm = insn->modrm.bytes[0]; > > + u8 modrm_mod = X86_MODRM_MOD(modrm); > > + u8 modrm_reg = X86_MODRM_REG(modrm); > > + > > + u8 prefix = insn->prefixes.bytes[0]; > > + > > + if (insn->opcode.bytes[0] != 0x0f) > > + return false; > > + > > + switch (insn->opcode.bytes[1]) { > > + case 0x01: > > + switch (insn->opcode.bytes[2]) { > > + case 0xc1: /* VMCALL */ > > + case 0xc2: /* VMLAUNCH */ > > + case 0xc3: /* VMRESUME */ > > + case 0xc4: /* VMXOFF */ > > + return true; > > + > > + default: > > + break; > > + } > > + break; > > + > > + case 0x78: /* VMREAD */ > > + case 0x79: /* VMWRITE */ > > + return true; > > + > > + case 0xc7: > > + /* VMPTRLD, VMPTRST, VMCLEAR, VMXON */ > > + if (modrm_mod == 0x03) > > + break; > > + > > + if ((modrm_reg == 6 && (!prefix || prefix == 0x66 || prefix == 0xf3)) || > > + (modrm_reg == 7 && (!prefix || prefix == 0xf3))) > > + return true; > > + > > + break; > > + > > + default: > > + break; > > + } > > + > > + return false; > > +} > > OK, so here is what you need ;) > > From 36f4f6aec623b0190fde95c8630a6a1d8c23ffc9 Mon Sep 17 00:00:00 2001 > From: Masami Hiramatsu > Date: Wed, 8 Apr 2020 01:04:41 +0900 > Subject: [PATCH] x86: insn: Add insn_is_vmx() > > Add insn_is_vmx() to identify the given instruction is > for VMX or not. This is simply identifying those instructions > by mnemonic pattern. > Hmm, I found that this is still not enough... since the inat_tables mixes the instruction attributes on same entry in group tables. It distinguishes opcodes by last-prefix variants, but not by MOD & R/M bits, since it is designed only for decoding instructions. Thank you, -- Masami Hiramatsu