From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756232AbbCRUtR (ORCPT ); Wed, 18 Mar 2015 16:49:17 -0400 Received: from mail.skyhub.de ([78.46.96.112]:48855 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754473AbbCRUtP (ORCPT ); Wed, 18 Mar 2015 16:49:15 -0400 Date: Wed, 18 Mar 2015 21:47:39 +0100 From: Borislav Petkov To: Denys Vlasenko Cc: Andy Lutomirski , Linus Torvalds , Steven Rostedt , Ingo Molnar , "H. Peter Anvin" , Oleg Nesterov , Frederic Weisbecker , Alexei Starovoitov , Will Drewry , Kees Cook , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] x86: get rid of KERNEL_STACK_OFFSET Message-ID: <20150318204739.GD3249@pd.tnic> References: <1426708056-2785-1-git-send-email-dvlasenk@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1426708056-2785-1-git-send-email-dvlasenk@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 18, 2015 at 08:47:34PM +0100, Denys Vlasenko wrote: > PER_CPU_VAR(kernel_stack) was set up in a way where it points > five stack slots below the top of stack. > > Presumably, it was done to avoid one "sub $5*8,%rsp" > in syscall/sysenter code paths, where iret frame needs to be > created by hand. > > Ironically, none of them benefits from this optimization, > since all of them need to allocate additional data on stack > (struct pt_regs), so they still have to perform subtraction. > > This patch eliminates KERNEL_STACK_OFFSET. > > PER_CPU_VAR(kernel_stack) now points directly to top of stack. > pt_regs allocations are adjusted to allocate iret frame as well. > Hopefully we can merge it later with 32-bit specific > PER_CPU_VAR(cpu_current_top_of_stack) variable... > > Semi-mysterious expressions THREAD_INFO(%rsp,RIP) - "why RIP??" > are now replaced by more logical THREAD_INFO(%rsp,SIZEOF_PTREGS) - > "calculate thread_info's address using information that > rsp is SIZEOF_PTREGS bytes below the stack top". Can we please add those last two lines to the definition of THREAD_INFO in the header? It is good to have. Thanks. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --