From: kernel test robot <lkp@intel.com>
To: Levi Yun <yeoreum.yun@arm.com>,
peterz@infradead.org, mark.rutland@arm.com,
james.clark@linaro.org, rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, mingo@elte.hu
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Levi Yun <yeoreum.yun@arm.com>
Subject: Re: [PATCH] trace/trace_event_perf: remove duplicate samples on the first tracepoint event
Date: Fri, 13 Sep 2024 05:02:48 +0800 [thread overview]
Message-ID: <202409130445.H7LIIGpd-lkp@intel.com> (raw)
In-Reply-To: <20240911122747.4168556-1-yeoreum.yun@arm.com>
Hi Levi,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.11-rc7 next-20240912]
[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/Levi-Yun/trace-trace_event_perf-remove-duplicate-samples-on-the-first-tracepoint-event/20240911-202917
base: linus/master
patch link: https://lore.kernel.org/r/20240911122747.4168556-1-yeoreum.yun%40arm.com
patch subject: [PATCH] trace/trace_event_perf: remove duplicate samples on the first tracepoint event
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240913/202409130445.H7LIIGpd-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240913/202409130445.H7LIIGpd-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/202409130445.H7LIIGpd-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace_event_perf.c:360:24: error: use of undeclared identifier 'event'
360 | if (is_sampling_event(event)) {
| ^
1 error generated.
vim +/event +360 kernel/trace/trace_event_perf.c
351
352 int perf_trace_add(struct perf_event *p_event, int flags)
353 {
354 struct trace_event_call *tp_event = p_event->tp_event;
355 struct hw_perf_event *hwc = &p_event->hw;
356
357 if (!(flags & PERF_EF_START))
358 p_event->hw.state = PERF_HES_STOPPED;
359
> 360 if (is_sampling_event(event)) {
361 hwc->last_period = hwc->sample_period;
362 perf_swevent_set_period(p_event);
363 }
364
365 /*
366 * If TRACE_REG_PERF_ADD returns false; no custom action was performed
367 * and we need to take the default action of enqueueing our event on
368 * the right per-cpu hlist.
369 */
370 if (!tp_event->class->reg(tp_event, TRACE_REG_PERF_ADD, p_event)) {
371 struct hlist_head __percpu *pcpu_list;
372 struct hlist_head *list;
373
374 pcpu_list = tp_event->perf_events;
375 if (WARN_ON_ONCE(!pcpu_list))
376 return -EINVAL;
377
378 list = this_cpu_ptr(pcpu_list);
379 hlist_add_head_rcu(&p_event->hlist_entry, list);
380 }
381
382 return 0;
383 }
384
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-12 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 12:27 [PATCH] trace/trace_event_perf: remove duplicate samples on the first tracepoint event Levi Yun
2024-09-12 12:34 ` kernel test robot
2024-09-12 21:02 ` kernel test robot [this message]
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=202409130445.H7LIIGpd-lkp@intel.com \
--to=lkp@intel.com \
--cc=james.clark@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@elte.hu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yeoreum.yun@arm.com \
/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.