From: kbuild test robot <lkp@intel.com>
To: byungchul.park@lge.com
Cc: kbuild-all@01.org, mingo@kernel.org, peterz@infradead.org,
linux-kernel@vger.kernel.org, yuyang.du@intel.com,
pjt@google.com, efault@gmx.de, tglx@linutronix.de,
Byungchul Park <byungchul.park@lge.com>
Subject: Re: [PATCH 1/2] sched: make fair sched class can handle the cgroup change by other class
Date: Mon, 5 Oct 2015 17:37:55 +0800 [thread overview]
Message-ID: <201510051739.oGuI2Sw7%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444036584-14079-2-git-send-email-byungchul.park@lge.com>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
Hi Byungchul,
[auto build test ERROR on next-20151002 -- if it's inappropriate base, please ignore]
config: i386-randconfig-x009-201540 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/sched/fair.c: In function 'task_move_group_from_fair':
>> kernel/sched/fair.c:8094:3: error: implicit declaration of function '__update_load_avg' [-Werror=implicit-function-declaration]
__update_load_avg(cfs_rq->avg.last_update_time, task_cpu(p),
^
>> kernel/sched/fair.c:8094:27: error: 'struct cfs_rq' has no member named 'avg'
__update_load_avg(cfs_rq->avg.last_update_time, task_cpu(p),
^
>> kernel/sched/fair.c:8095:10: error: 'struct sched_entity' has no member named 'avg'
&se->avg, 0, 0, NULL);
^
kernel/sched/fair.c: In function 'task_move_group_to_fair':
kernel/sched/fair.c:8119:5: error: 'struct sched_entity' has no member named 'avg'
se->avg.last_update_time = cfs_rq->avg.last_update_time;
^
kernel/sched/fair.c:8119:36: error: 'struct cfs_rq' has no member named 'avg'
se->avg.last_update_time = cfs_rq->avg.last_update_time;
^
cc1: some warnings being treated as errors
vim +/__update_load_avg +8094 kernel/sched/fair.c
8088 * Detaching was already done by switched_from_fair() when
8089 * the task got off from the fair_sched_class. But now that
8090 * the base cfs_rq for aging is about to be changed, if we
8091 * enabled ATTACH_AGE_LOAD then we perform the aging here
8092 * with the old cfs_rq, as the cfs_rq is not changed yet.
8093 */
> 8094 __update_load_avg(cfs_rq->avg.last_update_time, task_cpu(p),
> 8095 &se->avg, 0, 0, NULL);
8096 }
8097 }
8098
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24445 bytes --]
next prev parent reply other threads:[~2015-10-05 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 9:16 [PATCH 0/2] sched: make fair class handle rq/group changes by outside byungchul.park
2015-10-05 9:16 ` [PATCH 1/2] sched: make fair sched class can handle the cgroup change by other class byungchul.park
2015-10-05 9:37 ` kbuild test robot [this message]
2015-10-13 9:06 ` Peter Zijlstra
2015-10-13 11:26 ` Byungchul Park
2015-10-13 12:04 ` Peter Zijlstra
2015-10-13 12:07 ` Peter Zijlstra
2015-10-13 23:58 ` Byungchul Park
2015-10-05 9:16 ` [PATCH 2/2] sched: make fair sched class can handle migration " byungchul.park
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=201510051739.oGuI2Sw7%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=byungchul.park@lge.com \
--cc=efault@gmx.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=yuyang.du@intel.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 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®