From: kbuild test robot <lkp@intel.com>
To: cl@rock-chips.com
Cc: juri.lelli@redhat.com, mark.rutland@arm.com, heiko@sntech.de,
geert+renesas@glider.be, peterz@infradead.org,
catalin.marinas@arm.com, bsegall@google.com, will@kernel.org,
mpe@ellerman.id.au, linux@armlinux.org.uk,
dietmar.eggemann@arm.com, ben.dooks@codethink.co.uk,
mgorman@suse.de, Liang Chen <cl@rock-chips.com>,
huangtao@rock-chips.com, keescook@chromium.org,
anshuman.khandual@arm.com, rostedt@goodmis.org, wad@chromium.org,
tglx@linutronix.de, surenb@google.com, mingo@redhat.com,
allison@lohutok.net, linux-arm-kernel@lists.infradead.org,
kbuild-all@lists.01.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, luto@amacapital.net,
george_davis@mentor.com, sudeep.holla@arm.com,
akpm@linux-foundation.org, info@metux.net,
kstewart@linuxfoundation.org
Subject: Re: [PATCH v1 1/1] sched/fair: do not preempt current task if it is going to call schedule()
Date: Thu, 5 Mar 2020 21:33:10 +0800 [thread overview]
Message-ID: <202003052114.22Uw6Ht0%lkp@intel.com> (raw)
In-Reply-To: <20200305081611.29323-2-cl@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 3701 bytes --]
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on arm64/for-next/core tip/auto-latest linus/master v5.6-rc4 next-20200305]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/cl-rock-chips-com/wait_task_inactive-spend-too-much-time-on-system-startup/20200305-201639
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a0f03b617c3b2644d3d47bf7d9e60aed01bd5b10
config: riscv-randconfig-a001-20200305 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from arch/riscv/kernel/asm-offsets.c:10:0:
include/linux/sched.h: In function 'set_tsk_going_to_sched':
include/linux/sched.h:1776:27: error: 'TIF_GOING_TO_SCHED' undeclared (first use in this function); did you mean 'TIF_NEED_RESCHED'?
set_tsk_thread_flag(tsk, TIF_GOING_TO_SCHED);
^~~~~~~~~~~~~~~~~~
TIF_NEED_RESCHED
include/linux/sched.h:1776:27: note: each undeclared identifier is reported only once for each function it appears in
include/linux/sched.h: In function 'clear_tsk_going_to_sched':
include/linux/sched.h:1781:29: error: 'TIF_GOING_TO_SCHED' undeclared (first use in this function); did you mean 'TIF_NEED_RESCHED'?
clear_tsk_thread_flag(tsk, TIF_GOING_TO_SCHED);
^~~~~~~~~~~~~~~~~~
TIF_NEED_RESCHED
In file included from arch/riscv/include/asm/bug.h:9:0,
from include/linux/bug.h:5,
from arch/riscv/include/asm/current.h:13,
from include/linux/sched.h:12,
from arch/riscv/kernel/asm-offsets.c:10:
include/linux/sched.h: In function 'test_tsk_going_to_sched':
include/linux/sched.h:1786:44: error: 'TIF_GOING_TO_SCHED' undeclared (first use in this function); did you mean 'TIF_NEED_RESCHED'?
return unlikely(test_tsk_thread_flag(tsk, TIF_GOING_TO_SCHED));
^
include/linux/compiler.h:33:34: note: in definition of macro '__branch_check__'
______r = __builtin_expect(!!(x), expect); \
^
>> include/linux/sched.h:1786:9: note: in expansion of macro 'unlikely'
return unlikely(test_tsk_thread_flag(tsk, TIF_GOING_TO_SCHED));
^~~~~~~~
make[2]: *** [scripts/Makefile.build:101: arch/riscv/kernel/asm-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1112: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:179: sub-make] Error 2
21 real 5 user 9 sys 70.27% cpu make prepare
vim +/unlikely +1786 include/linux/sched.h
1783
1784 static inline int test_tsk_going_to_sched(struct task_struct *tsk)
1785 {
> 1786 return unlikely(test_tsk_thread_flag(tsk, TIF_GOING_TO_SCHED));
1787 }
1788
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32719 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-05 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 8:16 [PATCH v1 0/1] wait_task_inactive() spend too much time on system startup cl
2020-03-05 8:16 ` [PATCH v1 1/1] sched/fair: do not preempt current task if it is going to call schedule() cl
2020-03-05 8:43 ` Kees Cook
2020-03-05 9:58 ` Peter Zijlstra
2020-03-05 17:30 ` Kees Cook
2020-03-05 13:22 ` kbuild test robot
2020-03-05 13:33 ` kbuild test robot [this message]
2020-03-05 13:33 ` kbuild test robot
2020-03-05 13:59 ` kbuild test robot
2020-03-05 14:38 ` kbuild test robot
2020-03-05 15:14 ` [kbuild-all] " Li, Philip
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=202003052114.22Uw6Ht0%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=allison@lohutok.net \
--cc=anshuman.khandual@arm.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=cl@rock-chips.com \
--cc=dietmar.eggemann@arm.com \
--cc=geert+renesas@glider.be \
--cc=george_davis@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=info@metux.net \
--cc=juri.lelli@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).