From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751728AbdKIGO6 (ORCPT ); Thu, 9 Nov 2017 01:14:58 -0500 Received: from mga11.intel.com ([192.55.52.93]:8227 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbdKIGO4 (ORCPT ); Thu, 9 Nov 2017 01:14:56 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,368,1505804400"; d="scan'208";a="5552788" Date: Wed, 8 Nov 2017 22:13:16 -0800 From: Ricardo Neri To: Linus Torvalds Cc: Denys Vlasenko , Paolo Bonzini , Peter Anvin , Borislav Petkov , Vlastimil Babka , Tony Luck , Fenghua Yu , Josh Poimboeuf , Borislav Petkov , Brian Gerst , Jonathan Corbet , "Ravi V. Shankar" , Chris Metcalf , Andrew Morton , Paul Gortmaker , Masami Hiramatsu , Andrew Lutomirski , Dave Hansen , ray.huang@amd.com, "Michael S. Tsirkin" , Linux Kernel Mailing List , Peter Zijlstra , Chen Yucong , Ingo Molnar , Jiri Slaby , Shuah Khan , Thomas Gleixner , "linux-tip-commits@vger.kernel.org" Subject: Re: [tip:x86/asm] x86/umip: Add emulation code for UMIP instructions Message-ID: <20171109061316.GE30507@voyager> References: <1509935277-22138-8-git-send-email-ricardo.neri-calderon@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed, Nov 08, 2017 at 08:34:45AM -0800, Linus Torvalds wrote: > On Wed, Nov 8, 2017 at 8:14 AM, Denys Vlasenko wrote: > > > > Can we avoid maintain emulation of these isns, by asking Wine to remove > > their use instead? > > If we ask the Wine people to remove the instruction use, that may mean > that we can avoid the emulation in four or five _years_ once everybody > has updated. > > But it wouldn't mean that we could avoid it today. > > We *do* probably want to print a warning about these instructions, > whether emulated or not. If emulated, we want to print a warning about > the emulation being expensive (as a nudge to the Wine people to not do > that), and if _not_ emulated, we'd want to print a warning about why > people suddenly got a SIGSEGV in case there are programs that use > those instructions that people didn't even think of. I am preparing a set of complementary patches now that the series made it to the tip tree. I can include these updates as well. > > But make it ratelimit the warning (perhaps at most once every few > minutes or whatever), so that people won't flood message logs just > because they have old stupid programs that use those things. Will do. Thanks and BR, Ricardo