Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yicong Yang <yangyicong@hisilicon.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Will Deacon <will@kernel.org>
Subject: [arm-perf:for-next/perf 1/8] drivers/perf/arm_pmu.c:932:17: error: call to undeclared function 'topology_core_has_smt'; ISO C99 and later do not support implicit function declarations
Date: Tue, 4 Nov 2025 16:30:08 +0800	[thread overview]
Message-ID: <202511041650.VXU1O1Zh-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git for-next/perf
head:   989b40b7578a2be7b0388522d33d751b257d59d9
commit: c3d78c34ad009a7cce57ae5b5c93e1bd03bb31a3 [1/8] perf: arm_pmuv3: Don't use PMCCNTR_EL0 on SMT cores
config: arm-mv78xx0_defconfig (https://download.01.org/0day-ci/archive/20251104/202511041650.VXU1O1Zh-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251104/202511041650.VXU1O1Zh-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/202511041650.VXU1O1Zh-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/perf/arm_pmu.c:932:17: error: call to undeclared function 'topology_core_has_smt'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     932 |         pmu->has_smt = topology_core_has_smt(cpumask_first(&pmu->supported_cpus));
         |                        ^
   1 error generated.


vim +/topology_core_has_smt +932 drivers/perf/arm_pmu.c

   919	
   920	int armpmu_register(struct arm_pmu *pmu)
   921	{
   922		int ret;
   923	
   924		ret = cpu_pmu_init(pmu);
   925		if (ret)
   926			return ret;
   927	
   928		/*
   929		 * By this stage we know our supported CPUs on either DT/ACPI platforms,
   930		 * detect the SMT implementation.
   931		 */
 > 932		pmu->has_smt = topology_core_has_smt(cpumask_first(&pmu->supported_cpus));
   933	
   934		if (!pmu->set_event_filter)
   935			pmu->pmu.capabilities |= PERF_PMU_CAP_NO_EXCLUDE;
   936	
   937		ret = perf_pmu_register(&pmu->pmu, pmu->name, -1);
   938		if (ret)
   939			goto out_destroy;
   940	
   941		pr_info("enabled with %s PMU driver, %d (%*pb) counters available%s\n",
   942			pmu->name, bitmap_weight(pmu->cntr_mask, ARMPMU_MAX_HWEVENTS),
   943			ARMPMU_MAX_HWEVENTS, &pmu->cntr_mask,
   944			has_nmi ? ", using NMIs" : "");
   945	
   946		kvm_host_pmu_init(pmu);
   947	
   948		return 0;
   949	
   950	out_destroy:
   951		cpu_pmu_destroy(pmu);
   952		return ret;
   953	}
   954	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-11-04  8:31 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=202511041650.VXU1O1Zh-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=will@kernel.org \
    --cc=yangyicong@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox