From: kernel test robot <lkp@intel.com>
To: Gabriele Monaco <gmonaco@redhat.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Gabriele Monaco <gmonaco@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH v2 03/11] sched: Add sched tracepoints for RV task model
Date: Fri, 14 Feb 2025 17:52:17 +0800 [thread overview]
Message-ID: <202502141719.Jdm44al4-lkp@intel.com> (raw)
In-Reply-To: <20250213090819.419470-4-gmonaco@redhat.com>
Hi Gabriele,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4dc1d1bec89864d8076e5ab314f86f46442bfb02]
url: https://github.com/intel-lab-lkp/linux/commits/Gabriele-Monaco/tracing-Fix-DECLARE_TRACE_CONDITION/20250213-171642
base: 4dc1d1bec89864d8076e5ab314f86f46442bfb02
patch link: https://lore.kernel.org/r/20250213090819.419470-4-gmonaco%40redhat.com
patch subject: [PATCH v2 03/11] sched: Add sched tracepoints for RV task model
config: arm-randconfig-001-20250214 (https://download.01.org/0day-ci/archive/20250214/202502141719.Jdm44al4-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502141719.Jdm44al4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502141719.Jdm44al4-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/sched/core.c:503:2: error: call to undeclared function '__do_trace_sched_set_state_tp'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
__do_trace_sched_set_state_tp(current, current->__state, state_value);
^
kernel/sched/core.c:503:2: note: did you mean 'trace_sched_set_state_tp'?
include/trace/events/sched.h:835:1: note: 'trace_sched_set_state_tp' declared here
DECLARE_TRACE_CONDITION(sched_set_state_tp,
^
include/linux/tracepoint.h:472:2: note: expanded from macro 'DECLARE_TRACE_CONDITION'
__DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
^
include/linux/tracepoint.h:409:2: note: expanded from macro '__DECLARE_TRACE'
__DECLARE_TRACE_COMMON(name, PARAMS(proto), PARAMS(args), PARAMS(data_proto))
^
include/linux/tracepoint.h:385:21: note: expanded from macro '__DECLARE_TRACE_COMMON'
static inline void trace_##name(proto) \
^
<scratch space>:84:1: note: expanded from here
trace_sched_set_state_tp
^
1 error generated.
vim +/__do_trace_sched_set_state_tp +503 kernel/sched/core.c
496
497 /*
498 * Do not call this function directly since it won't check if the tp is enabled.
499 * Call the helper macro trace_set_current_state instead.
500 */
501 void __do_trace_set_current_state(int state_value)
502 {
> 503 __do_trace_sched_set_state_tp(current, current->__state, state_value);
504 }
505 EXPORT_SYMBOL(__do_trace_set_current_state);
506
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-14 9:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 9:07 [PATCH v2 00/11] rv: Add scheduler specification monitors Gabriele Monaco
2025-02-13 9:07 ` [PATCH v2 01/11] tracing: Fix DECLARE_TRACE_CONDITION Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 02/11] rv: Add license identifiers to monitor files Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 03/11] sched: Add sched tracepoints for RV task model Gabriele Monaco
2025-02-14 8:00 ` kernel test robot
2025-02-14 11:15 ` Gabriele Monaco
2025-02-17 16:39 ` Steven Rostedt
2025-02-14 9:52 ` kernel test robot [this message]
2025-02-17 16:38 ` Steven Rostedt
2025-02-17 16:49 ` Peter Zijlstra
2025-02-17 17:16 ` Steven Rostedt
2025-02-18 7:06 ` Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 04/11] rv: Add option for nested monitors and include sched Gabriele Monaco
2025-02-16 22:39 ` kernel test robot
2025-02-17 6:56 ` Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 05/11] rv: Add sco and tss per-cpu monitors Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 06/11] rv: Add snroc per-task monitor Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 07/11] rv: Add scpd, snep and sncid per-cpu monitors Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 08/11] tools/rv: Add support for nested monitors Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 09/11] verification/dot2k: " Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 10/11] Documentation/rv: Add docs for the sched monitors Gabriele Monaco
2025-02-13 9:08 ` [PATCH v2 11/11] tools/rv: Allow rv list to filter for container Gabriele Monaco
-- strict thread matches above, loose matches on Subject: below --
2025-02-17 13:11 [PATCH v2 00/11] rv: Add scheduler specification monitors Gabriele Monaco
2025-02-17 13:11 ` [PATCH v2 03/11] sched: Add sched tracepoints for RV task model Gabriele Monaco
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=202502141719.Jdm44al4-lkp@intel.com \
--to=lkp@intel.com \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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