From: kernel test robot <lkp@intel.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/2] sched/fair: Introduce per-task io util boost
Date: Thu, 7 Mar 2024 14:20:41 +0800 [thread overview]
Message-ID: <202403071415.olRuAaBL-lkp@intel.com> (raw)
In-Reply-To: <20240304201625.100619-2-christian.loehle@arm.com>
Hi Christian,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on rafael-pm/linux-next peterz-queue/sched/core linus/master v6.8-rc7 next-20240306]
[cannot apply to rafael-pm/acpi-bus rafael-pm/devprop]
[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/Christian-Loehle/sched-fair-Introduce-per-task-io-util-boost/20240305-042115
base: tip/sched/core
patch link: https://lore.kernel.org/r/20240304201625.100619-2-christian.loehle%40arm.com
patch subject: [RFC PATCH 1/2] sched/fair: Introduce per-task io util boost
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20240307/202403071415.olRuAaBL-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240307/202403071415.olRuAaBL-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403071415.olRuAaBL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/sched/fair.c:6703:22: warning: 'io_boost_rq' defined but not used [-Wunused-function]
6703 | static unsigned long io_boost_rq(struct cfs_rq *cfs_rq)
| ^~~~~~~~~~~
vim +/io_boost_rq +6703 kernel/sched/fair.c
6702
> 6703 static unsigned long io_boost_rq(struct cfs_rq *cfs_rq)
6704 {
6705 int i;
6706
6707 for (i = IO_BOOST_LEVELS; i > 0; i--)
6708 if (atomic_read(&cfs_rq->io_boost_tasks[i - 1]))
6709 return i * IO_BOOST_UTIL_STEP;
6710 return 0;
6711 }
6712
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-07 6:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 20:16 [RFC PATCH 0/2] Introduce per-task io utilization boost Christian Loehle
2024-03-04 20:16 ` [RFC PATCH 1/2] sched/fair: Introduce per-task io util boost Christian Loehle
2024-03-07 6:20 ` kernel test robot [this message]
2024-03-25 3:30 ` Qais Yousef
2024-03-04 20:16 ` [RFC PATCH 2/2] cpufreq/schedutil: Remove iowait boost Christian Loehle
2024-03-18 14:07 ` Rafael J. Wysocki
2024-03-18 16:40 ` Christian Loehle
2024-03-18 17:08 ` Rafael J. Wysocki
2024-03-19 13:58 ` Christian Loehle
2024-03-25 2:37 ` Qais Yousef
2024-04-19 13:42 ` Christian Loehle
2024-04-29 11:18 ` Qais Yousef
2024-05-07 15:19 ` Christian Loehle
2024-05-12 15:29 ` Qais Yousef
2024-03-05 0:20 ` [RFC PATCH 0/2] Introduce per-task io utilization boost Bart Van Assche
2024-03-05 9:13 ` Christian Loehle
2024-03-05 18:36 ` Bart Van Assche
2024-03-06 10:49 ` Christian Loehle
2024-03-21 12:39 ` Qais Yousef
2024-03-21 17:57 ` Christian Loehle
2024-03-21 19:52 ` Bart Van Assche
2024-03-25 12:06 ` Christian Loehle
2024-03-25 17:23 ` Bart Van Assche
2024-03-25 2:53 ` Qais Yousef
2024-03-22 18:08 ` Vincent Guittot
2024-03-25 2:20 ` Qais Yousef
2024-03-25 17:18 ` Christian Loehle
2024-03-25 12:24 ` Christian Loehle
2024-03-28 10:09 ` Vincent Guittot
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=202403071415.olRuAaBL-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.loehle@arm.com \
--cc=oe-kbuild-all@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.