From: kernel test robot <[email protected]>
To: Frederic Weisbecker <[email protected]>
Cc: [email protected], [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected],
"Paul E. McKenney" <[email protected]>
Subject: [ammarfaizi2-block:paulmck/linux-rcu/context-tracking.2022.05.03a 54/58] kernel/context_tracking.c:91:4: error: call to undeclared function 'rcu_irq_work_resched'; ISO C99 and later do not support implicit function declarations
Date: Fri, 6 May 2022 03:56:06 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/context-tracking.2022.05.03a
head: 9527c561aed6424e77fd2a8827c37f1103c89177
commit: cc2a2df362d428cc4c660df04d3e3403562fafb2 [54/58] rcu/context-tracking: Move deferred nocb resched to context tracking
config: riscv-randconfig-c006-20220505 (https://download.01.org/0day-ci/archive/20220506/[email protected]/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 5e004fb787698440a387750db7f8028e7cb14cfc)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/ammarfaizi2/linux-block/commit/cc2a2df362d428cc4c660df04d3e3403562fafb2
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/context-tracking.2022.05.03a
git checkout cc2a2df362d428cc4c660df04d3e3403562fafb2
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All errors (new ones prefixed by >>):
In file included from kernel/context_tracking.c:18:
In file included from include/linux/context_tracking.h:6:
In file included from include/linux/vtime.h:5:
include/linux/context_tracking_state.h:51:29: error: incompatible pointer types passing 'enum ctx_state *' to parameter of type 'const atomic_t *' [-Werror,-Wincompatible-pointer-types]
return atomic_read_acquire(&ct->state);
^~~~~~~~~~
include/linux/atomic/atomic-instrumented.h:32:37: note: passing argument to parameter 'v' here
atomic_read_acquire(const atomic_t *v)
^
In file included from kernel/context_tracking.c:21:
In file included from include/linux/hardirq.h:11:
In file included from ./arch/riscv/include/generated/asm/hardirq.h:1:
In file included from include/asm-generic/hardirq.h:17:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/riscv/include/asm/io.h:136:
include/asm-generic/io.h:464:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __raw_readb(PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:477:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr));
~~~~~~~~~~ ^
include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu'
#define __le16_to_cpu(x) ((__force __u16)(__le16)(x))
^
In file included from kernel/context_tracking.c:21:
In file included from include/linux/hardirq.h:11:
In file included from ./arch/riscv/include/generated/asm/hardirq.h:1:
In file included from include/asm-generic/hardirq.h:17:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/riscv/include/asm/io.h:136:
include/asm-generic/io.h:490:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr));
~~~~~~~~~~ ^
include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu'
#define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
^
In file included from kernel/context_tracking.c:21:
In file included from include/linux/hardirq.h:11:
In file included from ./arch/riscv/include/generated/asm/hardirq.h:1:
In file included from include/asm-generic/hardirq.h:17:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/riscv/include/asm/io.h:136:
include/asm-generic/io.h:501:33: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writeb(value, PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:511:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:521:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:1024:55: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
return (port > MMIO_UPPER_LIMIT) ? NULL : PCI_IOBASE + port;
~~~~~~~~~~ ^
>> kernel/context_tracking.c:91:4: error: call to undeclared function 'rcu_irq_work_resched'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
rcu_irq_work_resched();
^
7 warnings and 2 errors generated.
vim +/rcu_irq_work_resched +91 kernel/context_tracking.c
51
52 /**
53 * __ct_user_enter - Inform the context tracking that the CPU is going
54 * to enter user or guest space mode.
55 *
56 * This function must be called right before we switch from the kernel
57 * to user or guest space, when it's guaranteed the remaining kernel
58 * instructions to execute won't use any RCU read side critical section
59 * because this function sets RCU in extended quiescent state.
60 */
61 void noinstr __ct_user_enter(enum ctx_state state)
62 {
63 lockdep_assert_irqs_disabled();
64
65 /* Kernel threads aren't supposed to go to userspace */
66 WARN_ON_ONCE(!current->mm);
67
68 if (!context_tracking_recursion_enter())
69 return;
70
71 if ( __this_cpu_read(context_tracking.state) != state) {
72 if (__this_cpu_read(context_tracking.active)) {
73 /*
74 * At this stage, only low level arch entry code remains and
75 * then we'll run in userspace. We can assume there won't be
76 * any RCU read-side critical section until the next call to
77 * user_exit() or ct_irq_enter(). Let's remove RCU's dependency
78 * on the tick.
79 */
80 if (state == CONTEXT_USER) {
81 instrumentation_begin();
82 trace_user_enter(0);
83 vtime_user_enter(current);
84 instrumentation_end();
85 }
86 /*
87 * Other than generic entry implementation, we may be past the last
88 * rescheduling opportunity in the entry code. Trigger a self IPI
89 * that will fire and reschedule once we resume in user/guest mode.
90 */
> 91 rcu_irq_work_resched();
92 rcu_user_enter();
93 }
94 /*
95 * Even if context tracking is disabled on this CPU, because it's outside
96 * the full dynticks mask for example, we still have to keep track of the
97 * context transitions and states to prevent inconsistency on those of
98 * other CPUs.
99 * If a task triggers an exception in userspace, sleep on the exception
100 * handler and then migrate to another CPU, that new CPU must know where
101 * the exception returns by the time we call exception_exit().
102 * This information can only be provided by the previous CPU when it called
103 * exception_enter().
104 * OTOH we can spare the calls to vtime and RCU when context_tracking.active
105 * is false because we know that CPU is not tickless.
106 */
107 __this_cpu_write(context_tracking.state, state);
108 }
109 context_tracking_recursion_exit();
110 }
111 EXPORT_SYMBOL_GPL(__ct_user_enter);
112
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-05 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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