From: kernel test robot <lkp@intel.com>
To: Minwoo Ahn <mwahn402@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Jinkyu Jeong <jinkyu@yonsei.ac.kr>,
Minwoo Ahn <mwahn402@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/core: Fix sampling period inconsistency across CPU migration
Date: Wed, 29 Apr 2026 15:34:34 +0800 [thread overview]
Message-ID: <202604291520.xGDlzjFN-lkp@intel.com> (raw)
In-Reply-To: <20260428115317.22839-1-mwahn402@gmail.com>
Hi Minwoo,
kernel test robot noticed the following build errors:
[auto build test ERROR on perf-tools-next/perf-tools-next]
[also build test ERROR on tip/perf/core perf-tools/perf-tools linus/master v7.1-rc1 next-20260428]
[cannot apply to acme/perf/core]
[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/Minwoo-Ahn/perf-core-Fix-sampling-period-inconsistency-across-CPU-migration/20260429-115721
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/20260428115317.22839-1-mwahn402%40gmail.com
patch subject: [PATCH] perf/core: Fix sampling period inconsistency across CPU migration
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20260429/202604291520.xGDlzjFN-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260429/202604291520.xGDlzjFN-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/202604291520.xGDlzjFN-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:95,
from include/linux/syscalls_api.h:1,
from kernel/sched/sched.h:64,
from kernel/sched/rq-offsets.c:5:
>> include/linux/perf_event.h:1166:9: error: unknown type name 'local64_t'; did you mean 'local_t'?
1166 | local64_t period_left;
| ^~~~~~~~~
| local_t
make[3]: *** [scripts/Makefile.build:184: kernel/sched/rq-offsets.s] Error 1
make[3]: Target 'prepare' not remade because of errors.
make[2]: *** [Makefile:1337: prepare0] Error 2
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +1166 include/linux/perf_event.h
1153
1154 #define perf_event_equal_task_ctx(a1, a2) \
1155 ((a1)->config == (a2)->config && \
1156 (a1)->sample_period == (a2)->sample_period)
1157
1158 /**
1159 * struct perf_task_context - per-task software event context
1160 *
1161 * Shared across per-CPU perf_event instances of the same task to
1162 * preserve period_left across CPU migrations.
1163 */
1164 struct perf_task_context {
1165 refcount_t refcount;
> 1166 local64_t period_left;
1167 };
1168
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-29 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:53 [PATCH] perf/core: Fix sampling period inconsistency across CPU migration Minwoo Ahn
2026-04-28 22:24 ` sashiko-bot
2026-04-29 7:34 ` 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=202604291520.xGDlzjFN-lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jinkyu@yonsei.ac.kr \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mwahn402@gmail.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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.