From: Ada Couprie Diaz <ada.coupriediaz@arm.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com>,
catalin.marinas@arm.com, will@kernel.org, oleg@redhat.com,
sstabellini@kernel.org, mark.rutland@arm.com,
puranjay@kernel.org, broonie@kernel.org, mbenes@suse.cz,
ryan.roberts@arm.com, akpm@linux-foundation.org,
chenl311@chinatelecom.cn, anshuman.khandual@arm.com,
kristina.martsenko@arm.com, liaochang1@huawei.com,
ardb@kernel.org, leitao@debian.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH -next v7 0/7] arm64: entry: Convert to generic irq entry
Date: Tue, 5 Aug 2025 16:08:24 +0100 [thread overview]
Message-ID: <6bd09b5b-9830-42b4-ad9e-9ad1e153e564@arm.com> (raw)
In-Reply-To: <20250729015456.3411143-1-ruanjinjie@huawei.com>
Hi Jinjie,
On 29/07/2025 02:54, Jinjie Ruan wrote:
> Since commit a70e9f647f50 ("entry: Split generic entry into generic
> exception and syscall entry") split the generic entry into generic irq
> entry and generic syscall entry, it is time to convert arm64 to use
> the generic irq entry. And ARM64 will be completely converted to generic
> entry in the upcoming patch series.
Note : I had to manually cherry-pick a70e9f647f50 when pulling the series
on top of the Linux Arm Kernel for-next/core branch, but there might be
something I'm missing here.
>
> The main convert steps are as follows:
> - Split generic entry into generic irq entry and generic syscall to
> make the single patch more concentrated in switching to one thing.
> - Make arm64 easier to use irqentry_enter/exit().
> - Make arm64 closer to the PREEMPT_DYNAMIC code of generic entry.
> - Switch to generic irq entry.
I reviewed the whole series and as expected it looks good ! Just a few nits
here and there and some clarifications that I think could be useful.
I'm not sure about the generic implementation of
`arch_irqentry_exit_need_resched()`
in patch 5, I would be tempted to move it to patch 7. I detail my
thoughts more
on the relevant patches, but I might be wrong and that feels like details :
I don't think the code itself has issues.
> It was tested ok with following test cases on QEMU virt platform:
> - Perf tests.
> - Different `dynamic preempt` mode switch.
> - Pseudo NMI tests.
> - Stress-ng CPU stress test.
> - MTE test case in Documentation/arch/arm64/memory-tagging-extension.rst
> and all test cases in tools/testing/selftests/arm64/mte/*.
>
> The test QEMU configuration is as follows:
>
> qemu-system-aarch64 \
> -M virt,gic-version=3,virtualization=on,mte=on \
> -cpu max,pauth-impdef=on \
> -kernel Image \
> -smp 8,sockets=1,cores=4,threads=2 \
> -m 512m \
> -nographic \
> -no-reboot \
> -device virtio-rng-pci \
> -append "root=/dev/vda rw console=ttyAMA0 kgdboc=ttyAMA0,115200 \
> earlycon preempt=voluntary irqchip.gicv3_pseudo_nmi=1" \
> -drive if=none,file=images/rootfs.ext4,format=raw,id=hd0 \
> -device virtio-blk-device,drive=hd0 \
>
I'll spend some time testing the series now, specifically given patch 6's
changes, but other than that everything I saw made sense and didn't look
like it would be of concern to me.
Thanks,
Ada
next prev parent reply other threads:[~2025-08-05 15:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 1:54 [PATCH -next v7 0/7] arm64: entry: Convert to generic irq entry Jinjie Ruan
2025-07-29 1:54 ` [PATCH -next v7 1/7] arm64: ptrace: Replace interrupts_enabled() with regs_irqs_disabled() Jinjie Ruan
2025-08-05 15:05 ` Ada Couprie Diaz
2025-08-06 2:31 ` Jinjie Ruan
2025-07-29 1:54 ` [PATCH -next v7 2/7] arm64: entry: Refactor the entry and exit for exceptions from EL1 Jinjie Ruan
2025-08-05 15:06 ` Ada Couprie Diaz
2025-08-06 2:49 ` Jinjie Ruan
2025-08-11 16:01 ` Ada Couprie Diaz
2025-08-12 11:01 ` Mark Rutland
2025-07-29 1:54 ` [PATCH -next v7 3/7] arm64: entry: Rework arm64_preempt_schedule_irq() Jinjie Ruan
2025-08-05 15:06 ` Ada Couprie Diaz
2025-07-29 1:54 ` [PATCH -next v7 4/7] arm64: entry: Use preempt_count() and need_resched() helper Jinjie Ruan
2025-08-05 15:06 ` Ada Couprie Diaz
2025-07-29 1:54 ` [PATCH -next v7 5/7] arm64: entry: Refactor preempt_schedule_irq() check code Jinjie Ruan
2025-08-05 15:06 ` Ada Couprie Diaz
2025-08-06 6:26 ` Jinjie Ruan
2025-08-06 6:39 ` Jinjie Ruan
2025-08-11 16:02 ` Ada Couprie Diaz
2025-08-11 16:02 ` Ada Couprie Diaz
2025-08-14 8:49 ` Jinjie Ruan
2025-08-12 11:13 ` Mark Rutland
2025-08-14 9:31 ` Jinjie Ruan
2025-07-29 1:54 ` [PATCH -next v7 6/7] arm64: entry: Move arm64_preempt_schedule_irq() into __exit_to_kernel_mode() Jinjie Ruan
2025-08-05 15:07 ` Ada Couprie Diaz
2025-07-29 1:54 ` [PATCH -next v7 7/7] arm64: entry: Switch to generic IRQ entry Jinjie Ruan
2025-08-05 15:07 ` Ada Couprie Diaz
2025-08-06 6:59 ` Jinjie Ruan
2025-08-05 15:08 ` Ada Couprie Diaz [this message]
2025-08-06 8:11 ` [PATCH -next v7 0/7] arm64: entry: Convert to generic irq entry Jinjie Ruan
2025-08-11 16:03 ` Ada Couprie Diaz
2025-08-14 9:37 ` Jinjie Ruan
2025-08-12 11:19 ` Mark Rutland
2025-08-14 9:39 ` 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=6bd09b5b-9830-42b4-ad9e-9ad1e153e564@arm.com \
--to=ada.coupriediaz@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenl311@chinatelecom.cn \
--cc=kristina.martsenko@arm.com \
--cc=leitao@debian.org \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=oleg@redhat.com \
--cc=puranjay@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=sstabellini@kernel.org \
--cc=will@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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