From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [POC][RFC][PATCH 2/3] ftrace: Add perf counters to function tracing
Date: Thu, 20 Nov 2025 19:39:34 +0800 [thread overview]
Message-ID: <202511201931.aqNiFonA-lkp@intel.com> (raw)
In-Reply-To: <20251118003531.805883570@kernel.org>
Hi Steven,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on trace/for-next]
[also build test WARNING on next-20251120]
[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.805883570%40kernel.org
patch subject: [POC][RFC][PATCH 2/3] ftrace: Add perf counters to function tracing
config: s390-randconfig-001-20251120 (https://download.01.org/0day-ci/archive/20251120/202511201931.aqNiFonA-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 0bba1e76581bad04e7d7f09f5115ae5e2989e0d9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251120/202511201931.aqNiFonA-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/202511201931.aqNiFonA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_functions.c:538:5: warning: 'CONFIG_PERF_EVENTS' is not defined, evaluates to 0 [-Wundef]
538 | #if CONFIG_PERF_EVENTS
| ^
1 warning generated.
vim +/CONFIG_PERF_EVENTS +538 kernel/trace/trace_functions.c
529
530 static struct tracer_opt func_opts[] = {
531 #ifdef CONFIG_STACKTRACE
532 { TRACER_OPT(func_stack_trace, TRACE_FUNC_OPT_STACK) },
533 #endif
534 { TRACER_OPT(func-no-repeats, TRACE_FUNC_OPT_NO_REPEATS) },
535 #ifdef CONFIG_FUNCTION_TRACE_ARGS
536 { TRACER_OPT(func-args, TRACE_FUNC_OPT_ARGS) },
537 #endif
> 538 #if CONFIG_PERF_EVENTS
539 { TRACER_OPT(func-cpu-cycles, TRACE_FUNC_OPT_PERF_CYCLES) },
540 { TRACER_OPT(func-cache-misses, TRACE_FUNC_OPT_PERF_CACHE) },
541 #endif
542 { } /* Always set a last empty entry */
543 };
544
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-20 11:40 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
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 [this message]
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=202511201931.aqNiFonA-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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.