From: kernel test robot <lkp@intel.com>
To: Xukai Wang <kingxukai@zohomail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v2] sched/proxy: Defer donor commit until after proxy resolution
Date: Sun, 16 Aug 2026 13:16:19 +0800 [thread overview]
Message-ID: <202608161357.Jthx08U8-lkp@intel.com> (raw)
In-Reply-To: <20260713-sched-proxy-v2-1-729170082633@zohomail.com>
Hi Xukai,
[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 tip/master peterz-queue/sched/core linus/master v7.2-rc7]
[cannot apply to tip/auto-latest next-20260814]
[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/Xukai-Wang/sched-proxy-Defer-donor-commit-until-after-proxy-resolution/20260814-163837
base: tip/sched/core
patch link: https://lore.kernel.org/r/20260713-sched-proxy-v2-1-729170082633%40zohomail.com
patch subject: [PATCH RFC v2] sched/proxy: Defer donor commit until after proxy resolution
config: alpha-defconfig (https://download.01.org/0day-ci/archive/20260816/202608161357.Jthx08U8-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260816/202608161357.Jthx08U8-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/202608161357.Jthx08U8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/sched/core.c:5103:13: warning: 'zap_balance_callbacks' defined but not used [-Wunused-function]
5103 | static void zap_balance_callbacks(struct rq *rq)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/zap_balance_callbacks +5103 kernel/sched/core.c
31cb1bc0dc9488 Rodrigo Siqueira 2017-12-15 5092
48fda62de67a1e John Stultz 2026-03-24 5093 /*
48fda62de67a1e John Stultz 2026-03-24 5094 * Only called from __schedule context
48fda62de67a1e John Stultz 2026-03-24 5095 *
48fda62de67a1e John Stultz 2026-03-24 5096 * There are some cases where we are going to re-do the action
48fda62de67a1e John Stultz 2026-03-24 5097 * that added the balance callbacks. We may not be in a state
48fda62de67a1e John Stultz 2026-03-24 5098 * where we can run them, so just zap them so they can be
48fda62de67a1e John Stultz 2026-03-24 5099 * properly re-added on the next time around. This is similar
48fda62de67a1e John Stultz 2026-03-24 5100 * handling to running the callbacks, except we just don't call
48fda62de67a1e John Stultz 2026-03-24 5101 * them.
48fda62de67a1e John Stultz 2026-03-24 5102 */
48fda62de67a1e John Stultz 2026-03-24 @5103 static void zap_balance_callbacks(struct rq *rq)
48fda62de67a1e John Stultz 2026-03-24 5104 {
48fda62de67a1e John Stultz 2026-03-24 5105 struct balance_callback *next, *head;
48fda62de67a1e John Stultz 2026-03-24 5106 bool found = false;
48fda62de67a1e John Stultz 2026-03-24 5107
48fda62de67a1e John Stultz 2026-03-24 5108 lockdep_assert_rq_held(rq);
48fda62de67a1e John Stultz 2026-03-24 5109
48fda62de67a1e John Stultz 2026-03-24 5110 head = rq->balance_callback;
48fda62de67a1e John Stultz 2026-03-24 5111 while (head) {
48fda62de67a1e John Stultz 2026-03-24 5112 if (head == &balance_push_callback)
48fda62de67a1e John Stultz 2026-03-24 5113 found = true;
48fda62de67a1e John Stultz 2026-03-24 5114 next = head->next;
48fda62de67a1e John Stultz 2026-03-24 5115 head->next = NULL;
48fda62de67a1e John Stultz 2026-03-24 5116 head = next;
48fda62de67a1e John Stultz 2026-03-24 5117 }
48fda62de67a1e John Stultz 2026-03-24 5118 rq->balance_callback = found ? &balance_push_callback : NULL;
48fda62de67a1e John Stultz 2026-03-24 5119 }
48fda62de67a1e John Stultz 2026-03-24 5120
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-16 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 6:21 [PATCH RFC v2] sched/proxy: Defer donor commit until proxy resolution Xukai Wang
2026-07-13 6:21 ` [PATCH RFC v2] sched/proxy: Defer donor commit until after " Xukai Wang
2026-08-10 10:50 ` Xukai Wang
2026-08-11 20:41 ` John Stultz
2026-08-12 5:51 ` Xukai Wang
2026-08-16 5:16 ` 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=202608161357.Jthx08U8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kingxukai@zohomail.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.