All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chen Jinghuang <chenjinghuang2@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v5 8/9] sched/fair: Steal work from an overloaded CPU when CPU goes idle
Date: Sun, 22 Mar 2026 20:09:31 +0800	[thread overview]
Message-ID: <202603222032.E2CS3R19-lkp@intel.com> (raw)
In-Reply-To: <20260320055920.2518389-9-chenjinghuang2@huawei.com>

Hi Chen,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc4]
[cannot apply to tip/sched/core peterz-queue/sched/core next-20260320]
[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/Chen-Jinghuang/sched-Provide-sparsemask-a-reduced-contention-bitmap/20260321-084706
base:   linus/master
patch link:    https://lore.kernel.org/r/20260320055920.2518389-9-chenjinghuang2%40huawei.com
patch subject: [RFC PATCH v5 8/9] sched/fair: Steal work from an overloaded CPU when CPU goes idle
config: nios2-allnoconfig (https://download.01.org/0day-ci/archive/20260322/202603222032.E2CS3R19-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260322/202603222032.E2CS3R19-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/202603222032.E2CS3R19-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> kernel/sched/fair.c:13310:12: error: redefinition of 'try_steal'
   13310 | static int try_steal(struct rq *dst_rq, struct rq_flags *dst_rf)
         |            ^~~~~~~~~
   kernel/sched/fair.c:5195:19: note: previous definition of 'try_steal' with type 'int(struct rq *, struct rq_flags *)'
    5195 | static inline int try_steal(struct rq *this_rq, struct rq_flags *rf)
         |                   ^~~~~~~~~
>> kernel/sched/fair.c:13310:12: warning: 'try_steal' defined but not used [-Wunused-function]
   13310 | static int try_steal(struct rq *dst_rq, struct rq_flags *dst_rf)
         |            ^~~~~~~~~


vim +/try_steal +13310 kernel/sched/fair.c

 13303	
 13304	/*
 13305	 * Try to steal a runnable CFS task from a CPU in the same LLC as @dst_rq,
 13306	 * and migrate it to @dst_rq.  rq_lock is held on entry and return, but
 13307	 * may be dropped in between.  Return 1 on success, 0 on failure, and -1
 13308	 * if a task in a different scheduling class has become runnable on @dst_rq.
 13309	 */
 13310	static int try_steal(struct rq *dst_rq, struct rq_flags *dst_rf)
 13311	{
 13312		int src_cpu;
 13313		int dst_cpu = dst_rq->cpu;
 13314		bool locked = true;
 13315		int stolen = 0;
 13316		struct sparsemask *overload_cpus;
 13317	
 13318		if (!sched_feat(STEAL))
 13319			return 0;
 13320	
 13321		if (!cpu_active(dst_cpu))
 13322			return 0;
 13323	
 13324		if (dst_rq->avg_idle < SCHED_STEAL_COST)
 13325			return 0;
 13326	
 13327		/* Get bitmap of overloaded CPUs in the same LLC as @dst_rq */
 13328	
 13329		rcu_read_lock();
 13330		overload_cpus = rcu_dereference(dst_rq->cfs_overload_cpus);
 13331		if (!overload_cpus) {
 13332			rcu_read_unlock();
 13333			return 0;
 13334		}
 13335	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-03-22 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  5:59 [RFC PATCH v5 0/9] steal tasks to improve CPU utilization Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 1/9] sched: Provide sparsemask, a reduced contention bitmap Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 2/9] sched/topology: Provide hooks to allocate data shared per LLC Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 3/9] sched/topology: Provide cfs_overload_cpus bitmap Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 4/9] sched/fair: Dynamically update cfs_overload_cpus Chen Jinghuang
2026-03-24 13:56   ` kernel test robot
2026-03-20  5:59 ` [RFC PATCH v5 5/9] sched/fair: Hoist idle_stamp up from idle_balance Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 6/9] sched/fair: Generalize the detach_task interface Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 7/9] sched/fair: Provide can_migrate_task_llc Chen Jinghuang
2026-03-20  5:59 ` [RFC PATCH v5 8/9] sched/fair: Steal work from an overloaded CPU when CPU goes idle Chen Jinghuang
2026-03-22 12:09   ` kernel test robot [this message]
2026-03-23  0:14   ` kernel test robot
2026-03-23  4:51   ` kernel test robot
2026-03-20  5:59 ` [RFC PATCH v5 9/9] sched/fair: Provide idle search schedstats Chen Jinghuang
2026-03-20  8:53 ` [RFC PATCH v5 0/9] steal tasks to improve CPU utilization Peter Zijlstra
2026-03-27 13:54   ` Valentin Schneider
2026-03-28  2:48   ` chenjinghuang
2026-04-20  4:01     ` chenjinghuang

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=202603222032.E2CS3R19-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chenjinghuang2@huawei.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.