[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZKaUtnv0HfTci1-_WekNkmJyNA3znx7cUgJW5NNDAYVg@mail.gmail.com>
Date: Mon, 28 Apr 2025 16:46:02 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: tglx@...utronix.de
Cc: ruanjinjie@...wei.com, catalin.marinas@....com, will@...nel.org,
oleg@...hat.com, sstabellini@...nel.org, peterz@...radead.org,
luto@...nel.org, linux-kernel@...r.kernel.org, arnd@...db.de,
paulmck@...nel.org, mingo@...hat.com, dietmar.eggemann@....com,
linux-arm-kernel@...ts.infradead.org, mark.rutland@....com,
joey.gouly@....com, kevin.brodsky@....com, dave.martin@....com
Subject: Re: [PATCH -next v6 1/8] entry: Split generic entry into generic
exception and syscall entry
Hi Thomas,
On Thu, Mar 20, 2025 at 3:26 PM Linus Walleij <linus.walleij@...aro.org> wrote:
> > Currently CONFIG_GENERIC_ENTRY enables both the generic exception
> > entry logic and the generic syscall entry logic, which are otherwise
> > loosely coupled.
> >
> > Introduce separate config options for these so that archtiectures can
> > select the two independently. This will make it easier for
> > architectures to migrate to generic entry code.
> >
> > Suggested-by: Mark Rutland <mark.rutland@....com>
> > Signed-off-by: Jinjie Ruan <ruanjinjie@...wei.com>
>
> If the generic entry maintainer (hi Thomas) thinks this patch is
> OK it would be nice to have it applied because it will also make
> the ARM32 transition to generic entry easier as we can work on
> exception and syscall entry each in isolation.
>
> Acked-by: Linus Walleij <linus.walleij@...aro.org>
Do you think this patch is something you could queue on some
tip branch for v6.16?
I don't know if either arm64 or arm32 is going anywhere with
generic entry for v6.16, but having this in-tree makes it easier
to split the task going forward. We can always pull it into some
branch or just wait for v6.16-rc1 to get this patch under our
patch stacks.
Yours,
Linus Walleij
Powered by blists - more mailing lists