From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751573AbbIQLRl (ORCPT ); Thu, 17 Sep 2015 07:17:41 -0400 Received: from foss.arm.com ([217.140.101.70]:40818 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751104AbbIQLRk (ORCPT ); Thu, 17 Sep 2015 07:17:40 -0400 Date: Thu, 17 Sep 2015 12:17:36 +0100 From: Catalin Marinas To: Jungseok Lee Cc: will.deacon@arm.com, linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com, takahiro.akashi@linaro.org, James Morse , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] arm64: Introduce IRQ stack Message-ID: <20150917111735.GN25444@e104818-lin.cambridge.arm.com> References: <1442155337-7020-1-git-send-email-jungseoklee85@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1442155337-7020-1-git-send-email-jungseoklee85@gmail.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 Sun, Sep 13, 2015 at 02:42:17PM +0000, Jungseok Lee wrote: > Currently, kernel context and interrupts are handled using a single > kernel stack navigated by sp_el1. This forces many systems to use > 16KB stack, not 8KB one. Low memory platforms naturally suffer from > memory pressure accompanied by performance degradation. > > This patch addresses the issue as introducing a separate percpu IRQ > stack to handle both hard and soft interrupts with two ground rules: > > - Utilize sp_el0 in EL1 context, which is not used currently > - Do not complicate current_thread_info calculation > > It is a core concept to trace struct thread_info using sp_el0 instead > of sp_el1. This approach helps arm64 align with other architectures > regarding object_is_on_stack() without additional complexity. I'm still trying to understand how this patch works. I initially thought that we would set SPSel = 0 while in kernel thread mode to make use of SP_EL0 but I can't find any such code. Do you still use SP_EL1 all the time and SP_EL0 just for temporary saving the thread stack? -- Catalin