From: kernel test robot <lkp@intel.com>
To: John Stultz <jstultz@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC][PATCH 1/2] sched: Avoid placing RT threads on cores handling long softirqs
Date: Fri, 12 Aug 2022 01:06:20 +0800 [thread overview]
Message-ID: <202208120033.qCqng8xp-lkp@intel.com> (raw)
In-Reply-To: <20220811015758.3001641-2-jstultz@google.com>
Hi John,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/sched/core]
[also build test WARNING on linus/master v5.19 next-20220811]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/John-Stultz/Softirq-rt-Optimizations/20220811-100030
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 8648f92a66a323ed01903d2cbb248cdbe2f312d9
config: arm64-randconfig-r002-20220810 (https://download.01.org/0day-ci/archive/20220812/202208120033.qCqng8xp-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 5f1c7e2cc5a3c07cbc2412e851a7283c1841f520)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://github.com/intel-lab-lkp/linux/commit/3fceb870d95188903796394cbe5fd2493ee872c6
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review John-Stultz/Softirq-rt-Optimizations/20220811-100030
git checkout 3fceb870d95188903796394cbe5fd2493ee872c6
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash kernel/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:45:
>> kernel/sched/rt.c:1634:6: warning: no previous prototype for function 'rt_task_fits_capacity_and_may_preempt' [-Wmissing-prototypes]
bool rt_task_fits_capacity_and_may_preempt(struct task_struct *p, int cpu)
^
kernel/sched/rt.c:1634:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
bool rt_task_fits_capacity_and_may_preempt(struct task_struct *p, int cpu)
^
static
1 warning generated.
vim +/rt_task_fits_capacity_and_may_preempt +1634 kernel/sched/rt.c
1633
> 1634 bool rt_task_fits_capacity_and_may_preempt(struct task_struct *p, int cpu)
1635 {
1636 return task_may_preempt(p, cpu) && rt_task_fits_capacity(p, cpu);
1637 }
1638
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-08-11 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 1:57 [RFC][PATCH 0/2] Softirq -rt Optimizations John Stultz
2022-08-11 1:57 ` [RFC][PATCH 1/2] sched: Avoid placing RT threads on cores handling long softirqs John Stultz
2022-08-11 2:11 ` Randy Dunlap
2022-08-11 2:15 ` John Stultz
2022-08-11 17:06 ` kernel test robot [this message]
2022-08-11 1:57 ` [RFC][PATCH 2/2] softirq: defer softirq processing to ksoftirqd if CPU is busy with RT John Stultz
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=202208120033.qCqng8xp-lkp@intel.com \
--to=lkp@intel.com \
--cc=jstultz@google.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
/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.