From: kernel test robot <lkp@intel.com>
To: lijianzhong <lijianzhong@xiaomi.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org, Todd Kjos <tkjos@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android12-5.10 2257/9999] kernel/sched/fair.c:4424:6: warning: no previous prototype for 'set_next_entity'
Date: Thu, 10 Mar 2022 16:14:11 +0800 [thread overview]
Message-ID: <202203101619.QCheEDyN-lkp@intel.com> (raw)
Hi lijianzhong,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-5.10
head: 786bcb11099e8926ac5b5270de844d01c394ab89
commit: 54f66141a8834e27601fe594d68a97db01bb86b6 [2257/9999] ANDROID: sched: Add vendor hooks for sched.
config: i386-tinyconfig (https://download.01.org/0day-ci/archive/20220310/202203101619.QCheEDyN-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/54f66141a8834e27601fe594d68a97db01bb86b6
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-5.10
git checkout 54f66141a8834e27601fe594d68a97db01bb86b6
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash kernel/printk/ kernel/sched/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/sched/fair.c:4424:6: warning: no previous prototype for 'set_next_entity' [-Wmissing-prototypes]
4424 | void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
| ^~~~~~~~~~~~~~~
kernel/sched/fair.c:5408:6: warning: no previous prototype for 'init_cfs_bandwidth' [-Wmissing-prototypes]
5408 | void init_cfs_bandwidth(struct cfs_bandwidth *cfs_b) {}
| ^~~~~~~~~~~~~~~~~~
kernel/sched/fair.c:11341:6: warning: no previous prototype for 'free_fair_sched_group' [-Wmissing-prototypes]
11341 | void free_fair_sched_group(struct task_group *tg) { }
| ^~~~~~~~~~~~~~~~~~~~~
kernel/sched/fair.c:11343:5: warning: no previous prototype for 'alloc_fair_sched_group' [-Wmissing-prototypes]
11343 | int alloc_fair_sched_group(struct task_group *tg, struct task_group *parent)
| ^~~~~~~~~~~~~~~~~~~~~~
kernel/sched/fair.c:11348:6: warning: no previous prototype for 'online_fair_sched_group' [-Wmissing-prototypes]
11348 | void online_fair_sched_group(struct task_group *tg) { }
| ^~~~~~~~~~~~~~~~~~~~~~~
kernel/sched/fair.c:11350:6: warning: no previous prototype for 'unregister_fair_sched_group' [-Wmissing-prototypes]
11350 | void unregister_fair_sched_group(struct task_group *tg) { }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/set_next_entity +4424 kernel/sched/fair.c
4423
> 4424 void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
4425 {
4426 /* 'current' is not kept within the tree. */
4427 if (se->on_rq) {
4428 /*
4429 * Any task has to be enqueued before it get to execute on
4430 * a CPU. So account for the time it spent waiting on the
4431 * runqueue.
4432 */
4433 update_stats_wait_end(cfs_rq, se);
4434 __dequeue_entity(cfs_rq, se);
4435 update_load_avg(cfs_rq, se, UPDATE_TG);
4436 }
4437
4438 update_stats_curr_start(cfs_rq, se);
4439 cfs_rq->curr = se;
4440
4441 /*
4442 * Track our maximum slice length, if the CPU's load is at
4443 * least twice that of our own weight (i.e. dont track it
4444 * when there are only lesser-weight tasks around):
4445 */
4446 if (schedstat_enabled() &&
4447 rq_of(cfs_rq)->cfs.load.weight >= 2*se->load.weight) {
4448 schedstat_set(se->statistics.slice_max,
4449 max((u64)schedstat_val(se->statistics.slice_max),
4450 se->sum_exec_runtime - se->prev_sum_exec_runtime));
4451 }
4452
4453 se->prev_sum_exec_runtime = se->sum_exec_runtime;
4454 }
4455 EXPORT_SYMBOL_GPL(set_next_entity);
4456
4457
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-10 8:14 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=202203101619.QCheEDyN-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=lijianzhong@xiaomi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tkjos@google.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.