[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <be50aec4-336b-5bb3-e8dc-7f5cd12b43d2@huawei.com>
Date: Sat, 31 Jan 2026 09:48:40 +0800
From: Jinjie Ruan <ruanjinjie@...wei.com>
To: Thomas Gleixner <tglx@...nel.org>, <catalin.marinas@....com>,
<will@...nel.org>, <oleg@...hat.com>, <peterz@...radead.org>,
<luto@...nel.org>, <shuah@...nel.org>, <kees@...nel.org>, <wad@...omium.org>,
<kevin.brodsky@....com>, <deller@....de>, <akpm@...ux-foundation.org>,
<charlie@...osinc.com>, <ldv@...ace.io>, <mark.rutland@....com>,
<anshuman.khandual@....com>, <song@...nel.org>, <ryan.roberts@....com>,
<thuth@...hat.com>, <ada.coupriediaz@....com>, <broonie@...nel.org>,
<pengcan@...inos.cn>, <liqiang01@...inos.cn>, <kmal@...k.li>,
<dvyukov@...gle.com>, <reddybalavignesh9979@...il.com>,
<richard.weiyang@...il.com>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH v11 13/14] entry: Inline syscall_exit_work() and
syscall_trace_enter()
On 2026/1/30 18:14, Thomas Gleixner wrote:
> On Wed, Jan 28 2026 at 11:19, Jinjie Ruan wrote:
>> After switch arm64 to Generic Entry, a new hotspot syscall_exit_work()
>> appeared because syscall_exit_work() is not inlined, so inline
>> syscall_exit_work(). Also inline syscall_trace_enter() to align with
>> syscall_exit_work().
>
> Has the same collision problem. I can pick that up and massage it on top
> of the pending time slice changes. Let me give it a test ride on x86...
Thank you very much, hopefully we'll see similar good results there too.
>
Powered by blists - more mailing lists