From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:perf/wip.self 9/9] arch/x86/events/core.c:2725:48: error: 'PERF_X86_EVENT_RDPMC_ALLOWED' undeclared; did you mean 'PERF_X86_EVENT_AUTO_RELOAD'?
Date: Sat, 15 Jan 2022 05:48:53 +0800 [thread overview]
Message-ID: <202201150505.POFRV19D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/wip.self
head: 1b4635e33f629e20b5bbecd62d27c9191d5ec390
commit: 1b4635e33f629e20b5bbecd62d27c9191d5ec390 [9/9] perf: Better track self-monitoring events
config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220115/202201150505.POFRV19D-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=1b4635e33f629e20b5bbecd62d27c9191d5ec390
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue perf/wip.self
git checkout 1b4635e33f629e20b5bbecd62d27c9191d5ec390
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86/events/core.c: In function 'arch_perf_update_userpage':
>> arch/x86/events/core.c:2725:48: error: 'PERF_X86_EVENT_RDPMC_ALLOWED' undeclared (first use in this function); did you mean 'PERF_X86_EVENT_AUTO_RELOAD'?
2725 | userpg->cap_user_rdpmc = !!(event->hw.flags & PERF_X86_EVENT_RDPMC_ALLOWED);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| PERF_X86_EVENT_AUTO_RELOAD
arch/x86/events/core.c:2725:48: note: each undeclared identifier is reported only once for each function it appears in
vim +2725 arch/x86/events/core.c
2718
2719 void arch_perf_update_userpage(struct perf_event *event,
2720 struct perf_event_mmap_page *userpg, u64 now)
2721 {
2722 struct cyc2ns_data data;
2723 u64 offset;
2724
> 2725 userpg->cap_user_rdpmc = !!(event->hw.flags & PERF_X86_EVENT_RDPMC_ALLOWED);
2726 userpg->pmc_width = x86_pmu.cntval_bits;
2727
2728 if (unlikely(!using_native_sched_clock() || !sched_clock_stable())) {
2729 userpg->cap_user_time = 0;
2730 userpg->cap_user_time_zero = 0;
2731 return;
2732 }
2733
2734 /* already set the time fields before */
2735 if (likely(userpg->cap_user_time))
2736 return;
2737
2738 cyc2ns_read_begin(&data);
2739
2740 offset = data.cyc2ns_offset + __sched_clock_offset;
2741
2742 /*
2743 * Internal timekeeping for enabled/running/stopped times
2744 * is always in the local_clock domain.
2745 */
2746 userpg->cap_user_time = 1;
2747 userpg->time_mult = data.cyc2ns_mul;
2748 userpg->time_shift = data.cyc2ns_shift;
2749 userpg->time_offset = offset - now;
2750
2751 /*
2752 * cap_user_time_zero doesn't make sense when we're using a different
2753 * time base for the records.
2754 */
2755 if (!event->attr.use_clockid) {
2756 userpg->cap_user_time_zero = 1;
2757 userpg->time_zero = offset;
2758 }
2759
2760 cyc2ns_read_end();
2761 }
2762
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-14 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202201150505.POFRV19D-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome