From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751155AbaI3WnV (ORCPT ); Tue, 30 Sep 2014 18:43:21 -0400 Received: from terminus.zytor.com ([198.137.202.10]:58460 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750717AbaI3WnU (ORCPT ); Tue, 30 Sep 2014 18:43:20 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: <542B2305.9060805@fds-team.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [PATCH 1/2] x86_64,entry: Filter RFLAGS.NT on entry from userspace From: "H. Peter Anvin" Date: Tue, 30 Sep 2014 15:42:38 -0700 To: Thomas Gleixner , Andy Lutomirski CC: Sebastian Lackner , X86 ML , Ingo Molnar , Anish Bhatt , "linux-kernel@vger.kernel.org" , Chuck Ebbert , stable@kernel.org Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Nicely enough we get the context switch benefit without any cost in the comon case of 64-bit apps. On September 30, 2014 3:27:41 PM PDT, Thomas Gleixner wrote: >On Tue, 30 Sep 2014, Andy Lutomirski wrote: >> It would certainly be possible to clear NT and retry IRET if IRET >> fails with NT set. This would have no overhead for anything >relevant. >> That would be this alternative from my 0/2 email: >> >> - Don't filter NT on sysenter. Instead, filter it on EFI entry >> and modify the IRET code to retry without NT set if NT was set. >> >> Thomas hpa, etc: any thoughts? > >Filter it right away. That's solid and obvious. Anything else is just >complex and prone for future brown paperbag failures. > >We get the context switch benefit from it, so there is some >compensation for the extra cycles. > >Thanks, > > tglx -- Sent from my mobile phone. Please pardon brevity and lack of formatting.