From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: [tip:sched/urgent 2/2] kernel/sched/fair.c:3785:23: error: 'struct cfs_rq' has no member named 'nr_queued'
Date: Sun, 9 Feb 2025 01:10:10 +0800 [thread overview]
Message-ID: <202502090110.YeF4kwO1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/urgent
head: 55294004b122c997591d9de8446f5a4c60402805
commit: 55294004b122c997591d9de8446f5a4c60402805 [2/2] sched/fair: Adhere to place_entity() constraints
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250209/202502090110.YeF4kwO1-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250209/202502090110.YeF4kwO1-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/202502090110.YeF4kwO1-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/sched/fair.c: In function 'reweight_entity':
>> kernel/sched/fair.c:3785:23: error: 'struct cfs_rq' has no member named 'nr_queued'
3785 | cfs_rq->nr_queued--;
| ^~
kernel/sched/fair.c:3816:23: error: 'struct cfs_rq' has no member named 'nr_queued'
3816 | cfs_rq->nr_queued++;
| ^~
vim +3785 kernel/sched/fair.c
3773
3774 static void reweight_entity(struct cfs_rq *cfs_rq, struct sched_entity *se,
3775 unsigned long weight)
3776 {
3777 bool curr = cfs_rq->curr == se;
3778
3779 if (se->on_rq) {
3780 /* commit outstanding execution time */
3781 update_curr(cfs_rq);
3782 update_entity_lag(cfs_rq, se);
3783 se->deadline -= se->vruntime;
3784 se->rel_deadline = 1;
> 3785 cfs_rq->nr_queued--;
3786 if (!curr)
3787 __dequeue_entity(cfs_rq, se);
3788 update_load_sub(&cfs_rq->load, se->load.weight);
3789 }
3790 dequeue_load_avg(cfs_rq, se);
3791
3792 /*
3793 * Because we keep se->vlag = V - v_i, while: lag_i = w_i*(V - v_i),
3794 * we need to scale se->vlag when w_i changes.
3795 */
3796 se->vlag = div_s64(se->vlag * se->load.weight, weight);
3797 if (se->rel_deadline)
3798 se->deadline = div_s64(se->deadline * se->load.weight, weight);
3799
3800 update_load_set(&se->load, weight);
3801
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-08 17:10 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=202502090110.YeF4kwO1-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®