From: kernel test robot <lkp@intel.com>
To: Jeson Gao <jeson.gao@unisoc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-acpi@vger.kernel.org,
devel@acpica.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Lukasz Luba <lukasz.luba@arm.com>
Subject: [rafael-pm:bleeding-edge 103/108] drivers/powercap/dtpm_cpu.c:83:29: error: implicit declaration of function 'sched_cpu_util'
Date: Thu, 6 Mar 2025 12:24:49 +0800 [thread overview]
Message-ID: <202503061203.vRnwilWZ-lkp@intel.com> (raw)
Hi Jeson,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head: 96791086aa226b85fe090573b9e3668ac53d5364
commit: 9144584c375e73a4fef6bde3ce399ad43e011b37 [103/108] PM: EM: Rework the depends on for CONFIG_ENERGY_MODEL
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20250306/202503061203.vRnwilWZ-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250306/202503061203.vRnwilWZ-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/202503061203.vRnwilWZ-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/powercap/dtpm_cpu.c: In function 'scale_pd_power_uw':
>> drivers/powercap/dtpm_cpu.c:83:29: error: implicit declaration of function 'sched_cpu_util' [-Wimplicit-function-declaration]
83 | sum_util += sched_cpu_util(cpu);
| ^~~~~~~~~~~~~~
vim +/sched_cpu_util +83 drivers/powercap/dtpm_cpu.c
0e8f68d7f04856 Daniel Lezcano 2020-12-08 70
eb82bace893169 Daniel Lezcano 2021-03-12 71 static u64 scale_pd_power_uw(struct cpumask *pd_mask, u64 power)
eb82bace893169 Daniel Lezcano 2021-03-12 72 {
bb4479994945e9 Dietmar Eggemann 2022-06-21 73 unsigned long max, sum_util = 0;
eb82bace893169 Daniel Lezcano 2021-03-12 74 int cpu;
eb82bace893169 Daniel Lezcano 2021-03-12 75
eb82bace893169 Daniel Lezcano 2021-03-12 76 /*
eb82bace893169 Daniel Lezcano 2021-03-12 77 * The capacity is the same for all CPUs belonging to
bb4479994945e9 Dietmar Eggemann 2022-06-21 78 * the same perf domain.
eb82bace893169 Daniel Lezcano 2021-03-12 79 */
bb4479994945e9 Dietmar Eggemann 2022-06-21 80 max = arch_scale_cpu_capacity(cpumask_first(pd_mask));
eb82bace893169 Daniel Lezcano 2021-03-12 81
bb4479994945e9 Dietmar Eggemann 2022-06-21 82 for_each_cpu_and(cpu, pd_mask, cpu_online_mask)
bb4479994945e9 Dietmar Eggemann 2022-06-21 @83 sum_util += sched_cpu_util(cpu);
bb4479994945e9 Dietmar Eggemann 2022-06-21 84
bb4479994945e9 Dietmar Eggemann 2022-06-21 85 return (power * ((sum_util << 10) / max)) >> 10;
eb82bace893169 Daniel Lezcano 2021-03-12 86 }
eb82bace893169 Daniel Lezcano 2021-03-12 87
:::::: The code at line 83 was first introduced by commit
:::::: bb4479994945e9170534389a7762eb56149320ac sched, drivers: Remove max param from effective_cpu_util()/sched_cpu_util()
:::::: TO: Dietmar Eggemann <dietmar.eggemann@arm.com>
:::::: CC: Peter Zijlstra <peterz@infradead.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-06 4:25 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=202503061203.vRnwilWZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=jeson.gao@unisoc.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjw@rjwysocki.net \
/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