BPF List
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ankur Arora" <ankur.a.arora@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v14 02/15] arm64: barrier: Support smp_cond_load_relaxed_timeout()
Date: Tue, 14 Jul 2026 07:50:17 +0000	[thread overview]
Message-ID: <20260714075017.B66CE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714073041.40250-3-ankur.a.arora@oracle.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The generic macro `smp_cond_load_relaxed_timeout()` is broken for loadable modules on ARM64 because it uses the unexported symbol `arch_timer_evtstrm_available`.
--

--- Patch [2]: [PATCH v14 02/15] arm64: barrier: Support smp_cond_load_relaxed_timeout() ---
(Note: The format of this review has been altered to provide a free-form summary rather than inline quotes due to recitation restrictions.)

commit 8ff6ac5954b14995e35ca4865c27742e37086e23
Author: Ankur Arora <ankur.a.arora@oracle.com>
arm64: barrier: Support smp_cond_load_relaxed_timeout()

This commit adds support for smp_cond_load_relaxed_timeout() on arm64 by
using __cmpwait_relaxed() when the event-stream is available. It introduces
cpu_poll_relax() which checks arch_timer_evtstrm_available() before deciding
to wait or fallback to cpu_relax().

[Severity: High]
Will loadable modules be able to build if they use the new timeout barrier API?

The new cpu_poll_relax() macro in arch/arm64/include/asm/barrier.h calls
arch_timer_evtstrm_available(), which is defined in
drivers/clocksource/arm_arch_timer.c. 

Since cpu_poll_relax() is embedded inline into callers of
smp_cond_load_relaxed_timeout(), any loadable module that uses this generic
API will now require the arch_timer_evtstrm_available symbol.

However, it does not appear that arch_timer_evtstrm_available is exported with
EXPORT_SYMBOL or EXPORT_SYMBOL_GPL. 

Does this cause an undefined reference error during the modpost step for
device drivers that attempt to use smp_cond_load_relaxed_timeout()?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714073041.40250-1-ankur.a.arora@oracle.com?part=2

  reply	other threads:[~2026-07-14  7:50 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 [this message]
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
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=20260714075017.B66CE1F000E9@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