[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201021124542.GL1551@shell.armlinux.org.uk>
Date: Wed, 21 Oct 2020 13:45:42 +0100
From: Russell King - ARM Linux admin <linux@...linux.org.uk>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Maninder Singh <maninder1.s@...sung.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Jian Cai <caij2003@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Marc Zyngier <maz@...nel.org>,
Valentin Schneider <valentin.schneider@....com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
Nathan Huckleberry <nhuck@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Dmitry Safonov <0x7f454c46@...il.com>,
Will Deacon <will@...nel.org>, v.narang@...sung.com,
a.sahrawat@...sung.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] arm: introduce IRQ stacks
On Wed, Oct 21, 2020 at 02:42:48PM +0200, Arnd Bergmann wrote:
> (also resending this reply from @kernel.org)
>
> On Fri, Oct 16, 2020 at 12:19 PM Arnd Bergmann <arnd@...db.de> wrote:
> > On Thu, Oct 8, 2020 at 9:20 AM Maninder Singh <maninder1.s@...sung.com> wrote:
> > >
> > > This patch adds code for switching to IRQ stack.
> > > IRQ stack and Kernel SVC stack have below design.
> > >
> > > IRQ STACK:-
> > > ------------ IRQ stack top
> > > | |
> > > ------------
> > > . .
> > > . .
> > > . .
> > > ------------
> > > | sp | <- irq_stack_base + 0x8
> > > ------------
> > > | fp | <- irq_stack_base + 0x4
> > > ------------
> > > |tinfo_ptr | /* pointer to thread info */
> > > irq_stack_ptr --> ------------ IRQ stack base
> > >
> > > Kernel SVC stack:-
> > > ------------ Kernel stack top
> > > | |
> > > ------------
> > > . .
> > > . .
> > > . .
> > > ------------
> > > | |
> > > | |
> > > ------------
> > > |tinfo_ptr | /* pointer to thread info */
> > > ------------ Kernel stack base
> >
> > The extra indirection doesn't look great, and I don't see any of the
> > other architectures need that. Since we can access percpu data
> > without going through thread_info, maybe doing the same as
> > x86 would work here:
> >
> > - define 'current' as 'this_cpu_read_stable(current_task);'
> > - convert to CONFIG_THREAD_INFO_IN_TASK
That means we need to also code that up in assembly - remember, we
need to access thread_info from assembly code.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists