From: kernel test robot <lkp@intel.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [qais-yousef:uclamp-max-aggregation 8/13] kernel/sched/core.c:5154:37: error: 'struct cfs_rq' has no member named 'decayed'
Date: Sat, 25 May 2024 02:25:18 +0800 [thread overview]
Message-ID: <202405250237.QAavVy5P-lkp@intel.com> (raw)
tree: https://github.com/qais-yousef/linux uclamp-max-aggregation
head: 3173a853e6c16e1dcb09d392ef1e9b5a06448696
commit: 6bd11d636f6b37b0351907d35552fe9a1965e0a2 [8/13] sched: Consolidate cpufreq updates
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20240525/202405250237.QAavVy5P-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240525/202405250237.QAavVy5P-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/202405250237.QAavVy5P-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/export.h:5,
from include/linux/linkage.h:7,
from include/linux/fs.h:5,
from include/linux/highmem.h:5,
from kernel/sched/core.c:9:
kernel/sched/core.c: In function 'update_cpufreq_ctx_switch':
>> kernel/sched/core.c:5154:37: error: 'struct cfs_rq' has no member named 'decayed'
5154 | if (unlikely(rq->cfs.decayed)) {
| ^
include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
77 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
kernel/sched/core.c:5155:32: error: 'struct cfs_rq' has no member named 'decayed'
5155 | rq->cfs.decayed = false;
| ^
vim +5154 kernel/sched/core.c
5137
5138 static inline void update_cpufreq_ctx_switch(struct rq *rq)
5139 {
5140 if (unlikely(current->sched_class == &stop_sched_class))
5141 return;
5142
5143 if (unlikely(current->sched_class == &idle_sched_class))
5144 return;
5145
5146 if (unlikely(task_has_idle_policy(current)))
5147 return;
5148
5149 if (likely(fair_policy(current->policy))) {
5150
5151 /*
5152 * Allow cpufreq updates once for every update_load_avg() decay.
5153 */
> 5154 if (unlikely(rq->cfs.decayed)) {
5155 rq->cfs.decayed = false;
5156 goto force_update;
5157 }
5158
5159 if (unlikely(current->in_iowait))
5160 goto force_update;
5161
5162 return;
5163 }
5164
5165 /* RT and DL should always send a freq update */
5166
5167 /* XXX ignore updates for sugov worker thread */
5168
5169 force_update:
5170
5171 /*
5172 * Request freq update after __balance_callbacks to take into account
5173 * any changes to rq.
5174 */
5175 cpufreq_update_util(rq, current->in_iowait ? SCHED_CPUFREQ_IOWAIT : 0);
5176 }
5177
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-24 18:26 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=202405250237.QAavVy5P-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qyousef@layalina.io \
/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.