From: kernel test robot <lkp@intel.com>
To: Andrea Righi <arighi@nvidia.com>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Refresh idle state when kicking CPUs
Date: Wed, 8 Jan 2025 08:17:49 +0800 [thread overview]
Message-ID: <202501080743.HLPZzVsv-lkp@intel.com> (raw)
In-Reply-To: <20250101182449.21517-1-arighi@nvidia.com>
Hi Andrea,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master v6.13-rc6 next-20250107]
[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/Andrea-Righi/sched_ext-Refresh-idle-state-when-kicking-CPUs/20250102-022650
base: tip/sched/core
patch link: https://lore.kernel.org/r/20250101182449.21517-1-arighi%40nvidia.com
patch subject: [PATCH] sched_ext: Refresh idle state when kicking CPUs
config: x86_64-buildonly-randconfig-005-20250108 (https://download.01.org/0day-ci/archive/20250108/202501080743.HLPZzVsv-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250108/202501080743.HLPZzVsv-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/202501080743.HLPZzVsv-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:63:
kernel/sched/ext.c: In function 'refresh_idle_state_on_kick':
>> kernel/sched/ext.c:6031:17: error: implicit declaration of function '__scx_update_idle'; did you mean 'scx_update_idle'? [-Werror=implicit-function-declaration]
6031 | __scx_update_idle(rq, true);
| ^~~~~~~~~~~~~~~~~
| scx_update_idle
cc1: some warnings being treated as errors
vim +6031 kernel/sched/ext.c
6020
6021 static void refresh_idle_state_on_kick(struct rq *rq)
6022 {
6023 lockdep_assert_rq_held(rq);
6024
6025 /*
6026 * If the CPU is idle and the local DSQ has no queued tasks, update
6027 * its idle state to prevent the CPU from staying busy even if it
6028 * returns back to idle without executing any task.
6029 */
6030 if (is_idle_task(rq->curr) && !rq->scx.local_dsq.nr)
> 6031 __scx_update_idle(rq, true);
6032 }
6033
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-01-08 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 18:24 [PATCH] sched_ext: Refresh idle state when kicking CPUs Andrea Righi
2025-01-02 22:33 ` Tejun Heo
2025-01-03 8:55 ` Andrea Righi
2025-01-03 21:39 ` Tejun Heo
2025-01-04 7:06 ` Andrea Righi
2025-01-06 18:53 ` Tejun Heo
2025-01-08 0:17 ` kernel test robot [this message]
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=202501080743.HLPZzVsv-lkp@intel.com \
--to=lkp@intel.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.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