From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Cc: <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: Thu, 14 Aug 2025 17:37:46 +0800 [thread overview]
Message-ID: <2530ba09-73eb-c0fd-5d77-4e6c5a0810a6@huawei.com> (raw)
In-Reply-To: <a3a8c0b8-e953-4c93-ab4d-0d9a4b3e47b1@arm.com>
On 2025/8/12 0:03, Ada Couprie Diaz wrote:
> On 06/08/2025 09:11, Jinjie Ruan wrote:
>
>> On 2025/8/5 23:08, Ada Couprie Diaz wrote:
>>> 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.
>> It seems that it is now in mainline v6.16-rc1 and linux-next but not
>> Linux Arm Kernel for-next/core branch.
> You're right, I misinterpreted the `-next` of the subject, thanks for the
> clarification !
>>> 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.
>> Thank you for the test and review.
>
> I've spent some time testing the series with a few different
> configurations,
> including PREEMPT_RT, pNMI, various lockup and hang detection options,
> UBSAN, shadow call stack, and various CONFIG_DEBUG_XYZ (focused on locks
> and IRQs), on both hardware (AMD Seattle) and KVM guests.
>
> I tried to generate a diverse set of interrupts (via debug exceptions,
> page faults, perf, kprobes, swapping, OoM) while loading the system with
> different workloads, some generating a lot of context switches : hackbench
> and signaltest from rt-tests[0], and mc-crusher[1], a memcached
> stress-test.
>
> I did not have any issues, nor any warning reported by the various
> debug features during all my hours of testing, so it looks good !
>
> Tested-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Thank you for your comprehensive testing and code review.
>
> Thank you for the series !
> Ada
>
> [0]: https://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git/
> [1]: https://github.com/memcached/mc-crusher
>
>
next prev parent reply other threads:[~2025-08-14 9:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 1:54 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 ` [PATCH -next v7 0/7] arm64: entry: Convert to generic irq entry Ada Couprie Diaz
2025-08-06 8:11 ` Jinjie Ruan
2025-08-11 16:03 ` Ada Couprie Diaz
2025-08-14 9:37 ` Jinjie Ruan [this message]
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=2530ba09-73eb-c0fd-5d77-4e6c5a0810a6@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=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=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
all inboxes | Powered by JetHome®