From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [POC][RFC][PATCH 1/3] tracing: Add perf events
Date: Thu, 20 Nov 2025 17:23:57 +0800 [thread overview]
Message-ID: <202511201604.uyinorJA-lkp@intel.com> (raw)
In-Reply-To: <20251118003531.644484343@kernel.org>
Hi Steven,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on trace/for-next]
[also build test ERROR on next-20251119]
[cannot apply to linus/master v6.18-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/tracing-Add-perf-events/20251118-083721
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20251118003531.644484343%40kernel.org
patch subject: [POC][RFC][PATCH 1/3] tracing: Add perf events
config: arc-randconfig-6001-20251120 (https://download.01.org/0day-ci/archive/20251120/202511201604.uyinorJA-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251120/202511201604.uyinorJA-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/202511201604.uyinorJA-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace_output.c: In function 'trace_perf_event_print':
>> kernel/trace/trace_output.c:1681:18: error: invalid use of undefined type 'struct perf_event_entry'
1681 | for (val = field->values; val < end; val++) {
| ^~
kernel/trace/trace_output.c:1682:19: error: invalid use of undefined type 'struct perf_event_entry'
1682 | if (val != field->values)
| ^~
>> kernel/trace/trace_output.c:1684:11: error: implicit declaration of function 'PERF_TRACE_VALUE' [-Werror=implicit-function-declaration]
1684 | value = PERF_TRACE_VALUE(*val);
| ^~~~~~~~~~~~~~~~
>> kernel/trace/trace_output.c:1685:11: error: implicit declaration of function 'PERF_TRACE_TYPE' [-Werror=implicit-function-declaration]
1685 | switch (PERF_TRACE_TYPE(*val)) {
| ^~~~~~~~~~~~~~~
>> kernel/trace/trace_output.c:1686:8: error: 'PERF_TRACE_CYCLES' undeclared (first use in this function)
1686 | case PERF_TRACE_CYCLES:
| ^~~~~~~~~~~~~~~~~
kernel/trace/trace_output.c:1686:8: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/trace/trace_output.c:1689:8: error: 'PERF_TRACE_CACHE' undeclared (first use in this function); did you mean 'PERF_TYPE_HW_CACHE'?
1689 | case PERF_TRACE_CACHE:
| ^~~~~~~~~~~~~~~~
| PERF_TYPE_HW_CACHE
kernel/trace/trace_output.c: In function 'trace_perf_event_raw':
kernel/trace/trace_output.c:1714:18: error: invalid use of undefined type 'struct perf_event_entry'
1714 | for (val = field->values; val < end; val++) {
| ^~
kernel/trace/trace_output.c:1715:19: error: invalid use of undefined type 'struct perf_event_entry'
1715 | if (val != field->values)
| ^~
cc1: some warnings being treated as errors
vim +1681 kernel/trace/trace_output.c
1665
1666 static enum print_line_t
1667 trace_perf_event_print(struct trace_iterator *iter, int flags,
1668 struct trace_event *event)
1669 {
1670 struct trace_entry *entry = iter->ent;
1671 struct trace_seq *s = &iter->seq;
1672 struct perf_event_entry *field;
1673 u64 value;
1674 u64 *val;
1675 u64 *end;
1676
1677 end = (u64 *)((long)iter->ent + iter->ent_size);
1678
1679 trace_assign_type(field, entry);
1680
> 1681 for (val = field->values; val < end; val++) {
1682 if (val != field->values)
1683 trace_seq_putc(s, ' ');
> 1684 value = PERF_TRACE_VALUE(*val);
> 1685 switch (PERF_TRACE_TYPE(*val)) {
> 1686 case PERF_TRACE_CYCLES:
1687 trace_seq_printf(s, "cpu_cycles: %lld", value);
1688 break;
> 1689 case PERF_TRACE_CACHE:
1690 trace_seq_printf(s, "cache_misses: %lld", value);
1691 break;
1692 default:
1693 trace_seq_printf(s, "unkown(%d): %lld",
1694 (int)PERF_TRACE_TYPE(*val), value);
1695 }
1696 }
1697 trace_seq_putc(s, '\n');
1698 return trace_handle_return(s);
1699 }
1700
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-20 9:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 0:29 [POC][RFC][PATCH 0/3] tracing: Add perf events to trace buffer Steven Rostedt
2025-11-18 0:29 ` [POC][RFC][PATCH 1/3] tracing: Add perf events Steven Rostedt
2025-11-18 8:35 ` Peter Zijlstra
2025-11-18 13:42 ` Steven Rostedt
2025-11-18 20:24 ` Steven Rostedt
2025-11-20 9:01 ` kernel test robot
2025-11-20 9:23 ` kernel test robot [this message]
2025-11-18 0:29 ` [POC][RFC][PATCH 2/3] ftrace: Add perf counters to function tracing Steven Rostedt
2025-11-20 11:39 ` kernel test robot
2025-11-18 0:29 ` [POC][RFC][PATCH 3/3] fgraph: Add perf counters to function graph tracer Steven Rostedt
2025-11-18 3:08 ` [POC][RFC][PATCH 0/3] tracing: Add perf events to trace buffer Masami Hiramatsu
2025-11-18 3:42 ` Steven Rostedt
2025-11-18 8:11 ` Masami Hiramatsu
2025-11-18 13:53 ` Steven Rostedt
2025-11-18 13:57 ` Steven Rostedt
2025-11-18 16:31 ` Steven Rostedt
2025-11-18 7:25 ` Namhyung Kim
2025-11-18 16:24 ` Steven Rostedt
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=202511201604.uyinorJA-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.