From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ti:ti-rt-linux-5.10.y 4522/9999] arch/x86/events/intel/lbr.c:729:16: error: too many arguments to function 'x86_get_pmu'
Date: Sat, 22 Jan 2022 20:22:15 +0800 [thread overview]
Message-ID: <202201221956.kthYuW0r-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-5.10.y
head: d19d8f329cd20e1e2d14f30ed08d6a1164e6e9d9
commit: 56bc20e5fc64d55c194475692ee60893a3f452a5 [4522/9999] perf/x86/lbr: Remove cpuc->lbr_xsave allocation from atomic context
config: i386-randconfig-a003 (https://download.01.org/0day-ci/archive/20220122/202201221956.kthYuW0r-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add ti git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
git fetch --no-tags ti ti-rt-linux-5.10.y
git checkout 56bc20e5fc64d55c194475692ee60893a3f452a5
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the ti/ti-rt-linux-5.10.y HEAD d19d8f329cd20e1e2d14f30ed08d6a1164e6e9d9 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
arch/x86/events/intel/lbr.c: In function 'reserve_lbr_buffers':
>> arch/x86/events/intel/lbr.c:729:16: error: too many arguments to function 'x86_get_pmu'
729 | kmem_cache = x86_get_pmu(cpu)->task_ctx_cache;
| ^~~~~~~~~~~
In file included from arch/x86/events/intel/lbr.c:9:
arch/x86/events/intel/../perf_event.h:900:13: note: declared here
900 | struct pmu *x86_get_pmu(void);
| ^~~~~~~~~~~
vim +/x86_get_pmu +729 arch/x86/events/intel/lbr.c
717
718 void reserve_lbr_buffers(void)
719 {
720 struct kmem_cache *kmem_cache;
721 struct cpu_hw_events *cpuc;
722 int cpu;
723
724 if (!static_cpu_has(X86_FEATURE_ARCH_LBR))
725 return;
726
727 for_each_possible_cpu(cpu) {
728 cpuc = per_cpu_ptr(&cpu_hw_events, cpu);
> 729 kmem_cache = x86_get_pmu(cpu)->task_ctx_cache;
730 if (!kmem_cache || cpuc->lbr_xsave)
731 continue;
732
733 cpuc->lbr_xsave = kmem_cache_alloc_node(kmem_cache, GFP_KERNEL,
734 cpu_to_node(cpu));
735 }
736 }
737
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
reply other threads:[~2022-01-22 12:22 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=202201221956.kthYuW0r-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.