From: Jinjie Ruan <ruanjinjie@huawei.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: <arnd@arndb.de>, <afd@ti.com>, <akpm@linux-foundation.org>,
<linus.walleij@linaro.org>, <eric.devolder@oracle.com>,
<robh@kernel.org>, <vincent.whitchurch@axis.com>,
<bhe@redhat.com>, <nico@fluxnic.net>, <ardb@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] ARM: support PREEMPT_DYNAMIC
Date: Thu, 1 Aug 2024 09:26:58 +0800 [thread overview]
Message-ID: <3855e3a4-769b-5162-0747-cf72b94f7089@huawei.com> (raw)
In-Reply-To: <ZqoOoUPDIeJX5M0e@shell.armlinux.org.uk>
On 2024/7/31 18:14, Russell King (Oracle) wrote:
> On Wed, Jul 31, 2024 at 06:03:11PM +0800, Jinjie Ruan wrote:
>> On 2024/7/31 16:24, Russell King (Oracle) wrote:
>>> On Wed, Jul 31, 2024 at 10:07:53AM +0800, Jinjie Ruan wrote:
>>>>> #ifdef CONFIG_PREEMPTION
>>>>> +#ifdef CONFIG_PREEMPT_DYNAMIC
>>>>> + bl need_irq_preemption
>>>>> + cmp r0, #0
>>>>> + beq 2f
>>>>> +#endif
>>>
>>> Depending on the interrupt rate, this can be regarded as a fast path,
>>> it would be nice if we could find a way to use static branches in
>>> assembly code.
>> It seems to be hard to use static keys in assembly code.
>>
>> By the way, currently, most architectures have simplified assembly code
>> and implemented its most functions in C functions. Does arm32 have this
>> plan?
>
> arm32 is effectively in maintenance mode; very little active development
> is occuring. So, there are no plans to change the code without good
> reason (as code changes without reason will needlessly affect its
> stability.)
Thank you for helping me with my question.
>
next prev parent reply other threads:[~2024-08-01 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:00 Jinjie Ruan
2024-07-31 2:07 ` Jinjie Ruan
2024-07-31 8:24 ` Russell King (Oracle)
2024-07-31 9:25 ` Jinjie Ruan
2024-07-31 10:03 ` Jinjie Ruan
2024-07-31 10:14 ` Russell King (Oracle)
2024-08-01 1:26 ` Jinjie Ruan [this message]
2024-08-23 15:56 ` Linus Walleij
2024-08-26 2:40 ` Jinjie Ruan
2024-08-02 11:44 ` Russell King (Oracle)
2024-08-05 2:00 ` 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=3855e3a4-769b-5162-0747-cf72b94f7089@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@fluxnic.net \
--cc=robh@kernel.org \
--cc=vincent.whitchurch@axis.com \
/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®