public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: tglx@linutronix.de, ruanjinjie@huawei.com,
	catalin.marinas@arm.com, oleg@redhat.com, sstabellini@kernel.org,
	peterz@infradead.org, luto@kernel.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de, paulmck@kernel.org,
	mingo@redhat.com, dietmar.eggemann@arm.com,
	linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
	joey.gouly@arm.com, kevin.brodsky@arm.com, dave.martin@arm.com
Subject: Re: [PATCH -next v6 1/8] entry: Split generic entry into generic exception and syscall entry
Date: Tue, 29 Apr 2025 16:03:54 +0100	[thread overview]
Message-ID: <20250429150353.GA26272@willie-the-truck> (raw)
In-Reply-To: <CACRpkdZKaUtnv0HfTci1-_WekNkmJyNA3znx7cUgJW5NNDAYVg@mail.gmail.com>

On Mon, Apr 28, 2025 at 04:46:02PM +0200, Linus Walleij wrote:
> Hi Thomas,
> 
> On Thu, Mar 20, 2025 at 3:26 PM Linus Walleij <linus.walleij@linaro.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@arm.com>
> > > Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.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@linaro.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.

Agreed, having the core part merged would be really helpful if possible.

Cheers,

Will


  reply	other threads:[~2025-04-29 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 12:59 [PATCH -next v6 0/8] arm64: entry: Convert to generic irq entry Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 1/8] entry: Split generic entry into generic exception and syscall entry Jinjie Ruan
2025-03-20 14:26   ` Linus Walleij
2025-04-28 14:46     ` Linus Walleij
2025-04-29 15:03       ` Will Deacon [this message]
2025-02-13 13:00 ` [PATCH -next v6 2/8] arm64: ptrace: Replace interrupts_enabled() with regs_irqs_disabled() Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 3/8] arm64: entry: Refactor the entry and exit for exceptions from EL1 Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 4/8] arm64: entry: Rework arm64_preempt_schedule_irq() Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 5/8] arm64: entry: Use preempt_count() and need_resched() helper Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 6/8] arm64: entry: Refactor preempt_schedule_irq() check code Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 7/8] arm64: entry: Move arm64_preempt_schedule_irq() into __exit_to_kernel_mode() Jinjie Ruan
2025-02-13 13:00 ` [PATCH -next v6 8/8] arm64: entry: Switch to generic IRQ entry Jinjie Ruan
2025-02-27 18:08   ` Valentin Schneider
2025-02-27 18:35     ` Mark Rutland
2025-02-27 21:29       ` Valentin Schneider
2025-04-14  9:13 ` [PATCH -next v6 0/8] arm64: entry: Convert to generic irq entry Jinjie Ruan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250429150353.GA26272@willie-the-truck \
    --to=will@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.martin@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ruanjinjie@huawei.com \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox