From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android12-5.10-2021-09 8044/10848] kernel/sched/fair.c:4424:6: warning: no previous prototype for function 'set_next_entity'
Date: Mon, 08 Nov 2021 09:16:43 +0800 [thread overview]
Message-ID: <202111080941.oJrLUWfz-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3188 bytes --]
tree: https://android.googlesource.com/kernel/common android12-5.10-2021-09
head: ece338aaa6b4bdf1c505c64f6b391e5cfabbfee5
commit: 54f66141a8834e27601fe594d68a97db01bb86b6 [8044/10848] ANDROID: sched: Add vendor hooks for sched.
config: x86_64-randconfig-r033-20210928 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project dc6e8dfdfe7efecfda318d43a06fae18b40eb498)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android12-5.10-2021-09
git checkout 54f66141a8834e27601fe594d68a97db01bb86b6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64
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 function 'set_next_entity' [-Wmissing-prototypes]
void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
^
kernel/sched/fair.c:4424:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
^
static
kernel/sched/fair.c:8365:19: warning: unused function 'check_misfit_status' [-Wunused-function]
static inline int check_misfit_status(struct rq *rq, struct sched_domain *sd)
^
2 warnings generated.
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, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 29929 bytes --]
reply other threads:[~2021-11-08 1:16 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=202111080941.oJrLUWfz-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.