From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756509AbcECVMN (ORCPT ); Tue, 3 May 2016 17:12:13 -0400 Received: from mail.skyhub.de ([78.46.96.112]:39399 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756136AbcECVMM (ORCPT ); Tue, 3 May 2016 17:12:12 -0400 Date: Tue, 3 May 2016 23:12:03 +0200 From: Borislav Petkov To: Dave Hansen Cc: Ingo Molnar , linux-kernel@vger.kernel.org, x86@kernel.org, Andy Lutomirski , Thomas Gleixner , "H. Peter Anvin" , Linus Torvalds Subject: Re: [PATCH] [RFC] x86: work around MPX Erratum Message-ID: <20160503211202.GA27604@pd.tnic> References: <20160502220341.9E8C34FC@viggo.jf.intel.com> <20160503064354.GA11112@gmail.com> <57291268.3060006@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <57291268.3060006@intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 03, 2016 at 02:04:40PM -0700, Dave Hansen wrote: > My concern was not necessarily with folks booting with 'nosmep', but Btw, does anything speak for even keeping that 'nosmep' thing? > with processors that have MPX present and SMEP fused off (or made > unavailable by a hypervisor) and which are unaffected by this issue. So we won't init MPX on those... > People would have to be very careful to never create a processor which > did not have SMEP but did have MPX, since MPX would effectively be > unusable on such a processor. We can disable that combination in qemu too, right? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.