From: Mark Rutland <mark.rutland@arm.com>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] entry: fix compile error in dynamic_irqentry_exit_cond_resched()
Date: Wed, 30 Mar 2022 10:04:48 +0100 [thread overview]
Message-ID: <YkQdMDlIt1iHWS3U@FVFF77S0Q05N> (raw)
In-Reply-To: <20220330084328.1805665-1-svens@linux.ibm.com>
On Wed, Mar 30, 2022 at 10:43:28AM +0200, Sven Schnelle wrote:
> kernel/entry/common.c: In function ‘dynamic_irqentry_exit_cond_resched’:
> kernel/entry/common.c:409:14: error: implicit declaration of function ‘static_key_unlikely’; did you mean ‘static_key_enable’? [-Werror=implicit-function-declaration]
> 409 | if (!static_key_unlikely(&sk_dynamic_irqentry_exit_cond_resched))
> | ^~~~~~~~~~~~~~~~~~~
> | static_key_enable
>
> static_key_unlikely() should be static_branch_unlikely().
>
> Fixes: 99cf983cc8bca ("sched/preempt: Add PREEMPT_DYNAMIC using static keys")
> Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Sorry about this. FWIW:
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
For context for others, this'll only show up on architectures which both use
the generic entry code and select CONFIG_HAVE_PREEMPT_DYNAMIC_KEY. Today, only
arm64 selects CONFIG_HAVE_PREEMPT_DYNAMIC_KEY, and it doesn't use the generic
entry code.
Sven, I assume you're looking at wiring this up on s390 or parisc?
Thanks,
Mark.
> ---
> kernel/entry/common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/entry/common.c b/kernel/entry/common.c
> index ef8d94a98b7e..371ee8914af1 100644
> --- a/kernel/entry/common.c
> +++ b/kernel/entry/common.c
> @@ -406,7 +406,7 @@ DEFINE_STATIC_CALL(irqentry_exit_cond_resched, raw_irqentry_exit_cond_resched);
> DEFINE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
> void dynamic_irqentry_exit_cond_resched(void)
> {
> - if (!static_key_unlikely(&sk_dynamic_irqentry_exit_cond_resched))
> + if (!static_branch_unlikely(&sk_dynamic_irqentry_exit_cond_resched))
> return;
> raw_irqentry_exit_cond_resched();
> }
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-03-30 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 8:43 Sven Schnelle
2022-03-30 9:04 ` Mark Rutland [this message]
2022-03-30 9:17 ` Sven Schnelle
2022-03-30 9:53 ` Mark Rutland
2022-03-30 10:01 ` Sven Schnelle
2022-04-05 8:22 ` [tip: sched/urgent] entry: Fix " tip-bot2 for Sven Schnelle
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=YkQdMDlIt1iHWS3U@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
/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®