From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754204AbdKNJfz (ORCPT ); Tue, 14 Nov 2017 04:35:55 -0500 Received: from terminus.zytor.com ([65.50.211.136]:47793 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754180AbdKNJfi (ORCPT ); Tue, 14 Nov 2017 04:35:38 -0500 Date: Tue, 14 Nov 2017 01:30:57 -0800 From: tip-bot for Ricardo Neri Message-ID: Cc: mingo@kernel.org, luto@kernel.org, pbonzini@redhat.com, peterz@infradead.org, bp@suse.de, tglx@linutronix.de, linux-kernel@vger.kernel.org, ravi.v.shankar@intel.com, ricardo.neri-calderon@linux.intel.com, torvalds@linux-foundation.org, tony.luck@intel.com, hpa@zytor.com Reply-To: tony.luck@intel.com, ricardo.neri-calderon@linux.intel.com, torvalds@linux-foundation.org, ravi.v.shankar@intel.com, linux-kernel@vger.kernel.org, hpa@zytor.com, pbonzini@redhat.com, luto@kernel.org, mingo@kernel.org, tglx@linutronix.de, bp@suse.de, peterz@infradead.org In-Reply-To: <1510640985-18412-2-git-send-email-ricardo.neri-calderon@linux.intel.com> References: <1510640985-18412-2-git-send-email-ricardo.neri-calderon@linux.intel.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:x86/urgent] x86/umip: Select X86_INTEL_UMIP by default Git-Commit-ID: 796ebc81b9931bfa293b4ca38ae28c21a363f4d0 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 796ebc81b9931bfa293b4ca38ae28c21a363f4d0 Gitweb: https://git.kernel.org/tip/796ebc81b9931bfa293b4ca38ae28c21a363f4d0 Author: Ricardo Neri AuthorDate: Mon, 13 Nov 2017 22:29:42 -0800 Committer: Ingo Molnar CommitDate: Tue, 14 Nov 2017 08:38:08 +0100 x86/umip: Select X86_INTEL_UMIP by default UMIP does cause any performance penalty to the vast majority of x86 code that does not use the legacy instructions affected by UMIP. Also describe UMIP more accurately and explain the behavior that can be expected by the (few) applications that use the affected instructions. Suggested-by: Ingo Molnar Signed-off-by: Ricardo Neri Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Linus Torvalds Cc: Paolo Bonzini Cc: Peter Zijlstra Cc: Ravi V. Shankar Cc: Thomas Gleixner Cc: Tony Luck Cc: ricardo.neri@intel.com Link: http://lkml.kernel.org/r/1510640985-18412-2-git-send-email-ricardo.neri-calderon@linux.intel.com [ Spelling fixes, rewrote the changelog. ] Signed-off-by: Ingo Molnar --- arch/x86/Kconfig | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index f08977d..a0623f0 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -1805,14 +1805,20 @@ config X86_SMAP If unsure, say Y. config X86_INTEL_UMIP - def_bool n + def_bool y depends on CPU_SUP_INTEL prompt "Intel User Mode Instruction Prevention" if EXPERT ---help--- The User Mode Instruction Prevention (UMIP) is a security feature in newer Intel processors. If enabled, a general - protection fault is issued if the instructions SGDT, SLDT, - SIDT, SMSW and STR are executed in user mode. + protection fault is issued if the SGDT, SLDT, SIDT, SMSW + or STR instructions are executed in user mode. These instructions + unnecessarily expose information about the hardware state. + + The vast majority of applications do not use these instructions. + For the very few that do, software emulation is provided in + specific cases in protected and virtual-8086 modes. Emulated + results are dummy. config X86_INTEL_MPX prompt "Intel MPX (Memory Protection Extensions)"