linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jinjie Ruan <ruanjinjie@huawei.com>
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: Wed, 31 Jul 2024 09:24:32 +0100	[thread overview]
Message-ID: <Zqn0wL5iScf455O5@shell.armlinux.org.uk> (raw)
In-Reply-To: <79a3de7c-21da-12ce-8372-9c9029c237ac@huawei.com>

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.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!


  reply	other threads:[~2024-07-31  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  9:00 [PATCH] ARM: support PREEMPT_DYNAMIC Jinjie Ruan
2024-07-31  2:07 ` Jinjie Ruan
2024-07-31  8:24   ` Russell King (Oracle) [this message]
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
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=Zqn0wL5iScf455O5@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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=nico@fluxnic.net \
    --cc=robh@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --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;
as well as URLs for NNTP newsgroup(s).