[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a12DXAP6NhHxf9Fr9pxJ-yjE5L7KsAMNEtSJ01xR6asXw@mail.gmail.com>
Date: Wed, 21 Oct 2020 14:55:29 +0200
From: Arnd Bergmann <arnd@...nel.org>
To: Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc: Arnd Bergmann <arnd@...nel.org>,
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 2:45 PM Russell King - ARM Linux admin
<linux@...linux.org.uk> wrote:
> On Wed, Oct 21, 2020 at 02:42:48PM +0200, Arnd Bergmann wrote:
> > >
> > > - 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.
Are there any obvious places that need patching aside from
.macro get_thread_info? I did expect the above conversion to
be somewhat more complicated than Maninder's original patch,
but that part seems easy enough.
Arnd
Powered by blists - more mailing lists