From: sashiko-bot@kernel.org
To: "Ankur Arora" <ankur.a.arora@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v14 13/15] arm64/delay: enable testing smp_cond_load_relaxed_timeout()
Date: Tue, 14 Jul 2026 07:58:56 +0000 [thread overview]
Message-ID: <20260714075857.971F71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714073041.40250-14-ankur.a.arora@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Conditionally exporting `__delay_cycles` and `arch_timer_evtstrm_available` only for KUnit prevents standard kernel modules from using generic atomic timeout APIs on arm64.
--
--- Patch [13]: [PATCH v14 13/15] arm64/delay: enable testing smp_cond_load_relaxed_timeout() ---
commit 66ad403e3794b9907fdbe044468423d2877131a1
Author: Ankur Arora <ankur.a.arora@oracle.com>
arm64/delay: enable testing smp_cond_load_relaxed_timeout()
This commit exports __delay_cycles() and arch_timer_evtstrm_available()
using EXPORT_SYMBOL_IF_KUNIT() to allow testing barrier timeout functions
as a module.
> diff --git a/arch/arm64/lib/delay.c b/arch/arm64/lib/delay.c
> index c660a7ea26dd6..dfb102ce30098 100644
> --- a/arch/arm64/lib/delay.c
> +++ b/arch/arm64/lib/delay.c
[ ... ]
> @@ -30,6 +31,7 @@ u64 notrace __delay_cycles(void)
> guard(preempt_notrace)();
> return __arch_counter_get_cntvct_stable();
> }
> +EXPORT_SYMBOL_IF_KUNIT(__delay_cycles);
[Severity: Medium]
Will this cause linking errors for standard kernel modules that use generic
atomic timeout APIs when CONFIG_KUNIT is disabled?
If a module uses macros like smp_cond_load_relaxed_timeout(), they expand
inline into the compilation unit, which relies on __delay_cycles().
Restricting this export to KUnit could prevent non-test modules from
building on arm64.
>
> void __delay(unsigned long cycles)
> {
[ ... ]
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 90aeff44a2764..1de63e1a2cd2f 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
[ ... ]
> @@ -896,6 +897,7 @@ bool arch_timer_evtstrm_available(void)
> */
> return cpumask_test_cpu(raw_smp_processor_id(), &evtstrm_available);
> }
> +EXPORT_SYMBOL_IF_KUNIT(arch_timer_evtstrm_available);
[Severity: Medium]
Could this also cause modpost failures for standard modules?
Like __delay_cycles(), arch_timer_evtstrm_available() may be called by the
inline expansion of generic barrier macros. Exporting it only for KUnit
restricts these generic APIs from being used in standard modules.
>
> static struct arch_timer_kvm_info arch_timer_kvm_info;
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260714073041.40250-1-ankur.a.arora@oracle.com?part=13
next prev parent reply other threads:[~2026-07-14 7:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 7:30 [PATCH v14 00/15] barrier: Add smp_cond_load_{relaxed,acquire}_timeout() Ankur Arora
2026-07-14 7:30 ` [PATCH v14 01/15] asm-generic: barrier: Add smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:42 ` sashiko-bot
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 02/15] arm64: barrier: Support smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:50 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 03/15] arm64/delay: move some constants out to a separate header Ankur Arora
2026-07-14 7:30 ` [PATCH v14 04/15] arm64: support WFET in smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:53 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 05/15] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() Ankur Arora
2026-07-14 7:44 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 06/15] asm-generic: barrier: Add smp_cond_load_acquire_timeout() Ankur Arora
2026-07-14 7:53 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 07/15] atomic: Add atomic_cond_read_*_timeout() Ankur Arora
2026-07-14 7:47 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 08/15] locking/atomic: scripts: build atomic_long_cond_read_*_timeout() Ankur Arora
2026-07-14 7:30 ` [PATCH v14 09/15] bpf/rqspinlock: switch check_timeout() to a clock interface Ankur Arora
2026-07-14 7:30 ` [PATCH v14 10/15] bpf/rqspinlock: Use smp_cond_load_acquire_timeout() Ankur Arora
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 11/15] sched: add need-resched timed wait interface Ankur Arora
2026-07-14 7:30 ` [PATCH v14 12/15] cpuidle/poll_state: Wait for need-resched via tif_need_resched_relaxed_wait() Ankur Arora
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 13/15] arm64/delay: enable testing smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:58 ` sashiko-bot [this message]
2026-07-14 7:30 ` [PATCH v14 14/15] barrier: add tests for smp_cond_load_*_timeout() Ankur Arora
2026-07-14 7:55 ` sashiko-bot
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 15/15] barrier: add clock tests for smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 8:03 ` sashiko-bot
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=20260714075857.971F71F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ankur.a.arora@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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