From: kernel test robot <lkp@intel.com>
To: Lifeng Zheng <zhenglifeng1@huawei.com>,
catalin.marinas@arm.com, will@kernel.org, rafael@kernel.org,
viresh.kumar@linaro.org, beata.michalska@arm.com,
sudeep.holla@arm.com
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
jonathan.cameron@huawei.com, vincent.guittot@linaro.org,
yangyicong@hisilicon.com, zhanjie9@hisilicon.com,
lihuisong@huawei.com, yubowen8@huawei.com,
linhongye@h-partners.com, zhenglifeng1@huawei.com
Subject: Re: [PATCH v3 3/3] arm64: topology: Setup AMU FIE for online CPUs only
Date: Wed, 6 Aug 2025 21:45:30 +0800 [thread overview]
Message-ID: <202508062150.aKsrWjHB-lkp@intel.com> (raw)
In-Reply-To: <20250805093330.3715444-4-zhenglifeng1@huawei.com>
Hi Lifeng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on rafael-pm/linux-next rafael-pm/bleeding-edge arm/for-next arm/fixes kvmarm/next soc/for-next linus/master v6.16 next-20250806]
[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/Lifeng-Zheng/arm64-topology-Set-scale-freq-source-only-for-the-CPUs-that-have-not-been-set-before/20250806-101537
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
patch link: https://lore.kernel.org/r/20250805093330.3715444-4-zhenglifeng1%40huawei.com
patch subject: [PATCH v3 3/3] arm64: topology: Setup AMU FIE for online CPUs only
config: arm64-randconfig-003-20250806 (https://download.01.org/0day-ci/archive/20250806/202508062150.aKsrWjHB-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250806/202508062150.aKsrWjHB-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/202508062150.aKsrWjHB-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/arm64/kernel/topology.c: In function 'cpuhp_topology_online':
arch/arm64/kernel/topology.c:409:34: error: implicit declaration of function 'cpufreq_cpu_get_raw_no_check'; did you mean 'cpufreq_cpu_get_raw'? [-Werror=implicit-function-declaration]
409 | struct cpufreq_policy *policy = cpufreq_cpu_get_raw_no_check(cpu);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| cpufreq_cpu_get_raw
>> arch/arm64/kernel/topology.c:409:34: warning: initialization of 'struct cpufreq_policy *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
vim +409 arch/arm64/kernel/topology.c
406
407 static int cpuhp_topology_online(unsigned int cpu)
408 {
> 409 struct cpufreq_policy *policy = cpufreq_cpu_get_raw_no_check(cpu);
410
411 /*
412 * If the online CPUs are not all AMU FIE CPUs or the new one is already
413 * an AMU FIE one, no need to set it.
414 */
415 if (!policy || !cpumask_available(amu_fie_cpus) ||
416 !cpumask_subset(policy->cpus, amu_fie_cpus) ||
417 cpumask_test_cpu(cpu, amu_fie_cpus))
418 return 0;
419
420 /*
421 * If the new online CPU cannot pass this check, all the CPUs related to
422 * the same policy should be clear from amu_fie_cpus mask, otherwise they
423 * may use different source of the freq scale.
424 */
425 if (!freq_counters_valid(cpu)) {
426 topology_clear_scale_freq_source(SCALE_FREQ_SOURCE_ARCH,
427 policy->related_cpus);
428 cpumask_andnot(amu_fie_cpus, amu_fie_cpus, policy->related_cpus);
429 return 0;
430 }
431
432 cpumask_set_cpu(cpu, amu_fie_cpus);
433
434 topology_set_scale_freq_source(&amu_sfd, cpumask_of(cpu));
435
436 pr_debug("CPU[%u]: counter will be used for FIE.", cpu);
437
438 return 0;
439 }
440
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-06 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 9:33 [PATCH v3 0/3] arm64: topology: Setup AMU FIE for online CPUs only Lifeng Zheng
2025-08-05 9:33 ` [PATCH v3 1/3] arm64: topology: Set scale freq source only for the CPUs that have not been set before Lifeng Zheng
2025-08-05 9:33 ` [PATCH v3 2/3] cpufreq: Add a new function to get cpufreq policy without checking if the CPU is online Lifeng Zheng
2025-08-05 12:57 ` Rafael J. Wysocki
2025-08-05 13:32 ` zhenglifeng (A)
2025-08-05 9:33 ` [PATCH v3 3/3] arm64: topology: Setup AMU FIE for online CPUs only Lifeng Zheng
2025-08-06 9:55 ` Beata Michalska
2025-08-13 10:17 ` zhenglifeng (A)
2025-08-13 11:08 ` Beata Michalska
2025-08-06 13:45 ` kernel test robot
2025-08-06 13:45 ` 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=202508062150.aKsrWjHB-lkp@intel.com \
--to=lkp@intel.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linhongye@h-partners.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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.