From: kernel test robot <lkp@intel.com>
To: Wanpeng Li <kernellwp@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
K Prateek Nayak <kprateek.nayak@amd.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Wanpeng Li <wanpengli@tencent.com>
Subject: Re: [PATCH v2 2/9] sched/fair: Add rate-limiting and validation helpers
Date: Tue, 23 Dec 2025 05:12:38 +0800 [thread overview]
Message-ID: <202512230415.0RatyaQF-lkp@intel.com> (raw)
In-Reply-To: <20251219035334.39790-3-kernellwp@gmail.com>
Hi Wanpeng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kvm/queue]
[also build test WARNING on kvm/next tip/sched/core peterz-queue/sched/core tip/master linus/master v6.19-rc2 next-20251219]
[cannot apply to kvm/linux-next tip/auto-latest]
[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/Wanpeng-Li/sched-fair-Add-rate-limiting-and-validation-helpers/20251219-125353
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link: https://lore.kernel.org/r/20251219035334.39790-3-kernellwp%40gmail.com
patch subject: [PATCH v2 2/9] sched/fair: Add rate-limiting and validation helpers
config: openrisc-randconfig-r122-20251221 (https://download.01.org/0day-ci/archive/20251223/202512230415.0RatyaQF-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251223/202512230415.0RatyaQF-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/202512230415.0RatyaQF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/sched/fair.c:1158:49: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *running @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:1158:49: sparse: expected struct task_struct *running
kernel/sched/fair.c:1158:49: sparse: got struct task_struct [noderef] __rcu *curr
kernel/sched/fair.c:1194:33: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct sched_entity *se @@ got struct sched_entity [noderef] __rcu * @@
kernel/sched/fair.c:1194:33: sparse: expected struct sched_entity *se
kernel/sched/fair.c:1194:33: sparse: got struct sched_entity [noderef] __rcu *
kernel/sched/fair.c:1250:34: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct sched_entity const *se @@ got struct sched_entity [noderef] __rcu * @@
kernel/sched/fair.c:1250:34: sparse: expected struct sched_entity const *se
kernel/sched/fair.c:1250:34: sparse: got struct sched_entity [noderef] __rcu *
kernel/sched/fair.c:12991:9: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct sched_domain *[assigned] sd @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:12991:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:12991:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:8354:20: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct sched_domain *[assigned] sd @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:8354:20: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:8354:20: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:8558:9: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct sched_domain *[assigned] tmp @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:8558:9: sparse: expected struct sched_domain *[assigned] tmp
kernel/sched/fair.c:8558:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:8757:39: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *donor @@ got struct task_struct [noderef] __rcu *donor @@
kernel/sched/fair.c:8757:39: sparse: expected struct task_struct *donor
kernel/sched/fair.c:8757:39: sparse: got struct task_struct [noderef] __rcu *donor
kernel/sched/fair.c:8784:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct task_struct *tsk @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:8784:37: sparse: expected struct task_struct *tsk
kernel/sched/fair.c:8784:37: sparse: got struct task_struct [noderef] __rcu *curr
>> kernel/sched/fair.c:9089:20: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct task_struct *p_yielding @@ got struct task_struct [noderef] __rcu *donor @@
kernel/sched/fair.c:9089:20: sparse: expected struct task_struct *p_yielding
kernel/sched/fair.c:9089:20: sparse: got struct task_struct [noderef] __rcu *donor
kernel/sched/fair.c:9110:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *curr @@ got struct task_struct [noderef] __rcu *donor @@
kernel/sched/fair.c:9110:38: sparse: expected struct task_struct *curr
kernel/sched/fair.c:9110:38: sparse: got struct task_struct [noderef] __rcu *donor
kernel/sched/fair.c:10146:40: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct sched_domain *child @@ got struct sched_domain [noderef] __rcu *child @@
kernel/sched/fair.c:10146:40: sparse: expected struct sched_domain *child
kernel/sched/fair.c:10146:40: sparse: got struct sched_domain [noderef] __rcu *child
kernel/sched/fair.c:10774:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/fair.c:10774:22: sparse: struct task_struct [noderef] __rcu *
kernel/sched/fair.c:10774:22: sparse: struct task_struct *
kernel/sched/fair.c:12246:9: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct sched_domain *[assigned] sd @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:12246:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:12246:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:11884:44: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct sched_domain *sd_parent @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:11884:44: sparse: expected struct sched_domain *sd_parent
kernel/sched/fair.c:11884:44: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:12359:9: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct sched_domain *[assigned] sd @@ got struct sched_domain [noderef] __rcu *parent @@
kernel/sched/fair.c:12359:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:12359:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:6688:35: sparse: sparse: marked inline, but without a definition
kernel/sched/fair.c: note: in included file:
kernel/sched/sched.h:2647:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2647:9: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2647:9: sparse: struct task_struct *
kernel/sched/sched.h:2314:26: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2314:26: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2314:26: sparse: struct task_struct *
kernel/sched/sched.h:2303:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2303:25: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2303:25: sparse: struct task_struct *
kernel/sched/sched.h:2314:26: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2314:26: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2314:26: sparse: struct task_struct *
kernel/sched/sched.h:2314:26: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2314:26: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2314:26: sparse: struct task_struct *
kernel/sched/sched.h:2314:26: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:2314:26: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:2314:26: sparse: struct task_struct *
vim +9089 kernel/sched/fair.c
9064
9065 /*
9066 * Validate tasks for yield deboost operation.
9067 * Returns the yielding task on success, NULL on validation failure.
9068 *
9069 * Checks: feature enabled, valid target, same runqueue, target is fair class,
9070 * both on_rq. Called under rq->lock.
9071 *
9072 * Note: p_yielding (rq->donor) is guaranteed to be fair class by the caller
9073 * (yield_to_task_fair is only called when curr->sched_class == p->sched_class).
9074 */
9075 static struct task_struct __maybe_unused *
9076 yield_deboost_validate_tasks(struct rq *rq, struct task_struct *p_target)
9077 {
9078 struct task_struct *p_yielding;
9079
9080 if (!sysctl_sched_vcpu_debooster_enabled)
9081 return NULL;
9082
9083 if (!p_target)
9084 return NULL;
9085
9086 if (yield_deboost_rate_limit(rq))
9087 return NULL;
9088
> 9089 p_yielding = rq->donor;
9090 if (!p_yielding || p_yielding == p_target)
9091 return NULL;
9092
9093 if (p_target->sched_class != &fair_sched_class)
9094 return NULL;
9095
9096 if (task_rq(p_target) != rq)
9097 return NULL;
9098
9099 if (!p_target->se.on_rq || !p_yielding->se.on_rq)
9100 return NULL;
9101
9102 return p_yielding;
9103 }
9104
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-22 21:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 3:53 [PATCH v2 0/9] sched/kvm: Semantics-aware vCPU scheduling for oversubscribed KVM Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 1/9] sched: Add vCPU debooster infrastructure Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 2/9] sched/fair: Add rate-limiting and validation helpers Wanpeng Li
2025-12-22 21:12 ` kernel test robot [this message]
2026-01-04 4:09 ` Hillf Danton
2025-12-19 3:53 ` [PATCH v2 3/9] sched/fair: Add cgroup LCA finder for hierarchical yield Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 4/9] sched/fair: Add penalty calculation and application logic Wanpeng Li
2025-12-22 23:36 ` kernel test robot
2025-12-19 3:53 ` [PATCH v2 5/9] sched/fair: Wire up yield deboost in yield_to_task_fair() Wanpeng Li
2025-12-22 7:06 ` kernel test robot
2025-12-22 9:31 ` kernel test robot
2025-12-19 3:53 ` [PATCH v2 6/9] KVM: x86: Add IPI tracking infrastructure Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 7/9] KVM: x86/lapic: Integrate IPI tracking with interrupt delivery Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 8/9] KVM: Implement IPI-aware directed yield candidate selection Wanpeng Li
2025-12-19 3:53 ` [PATCH v2 9/9] KVM: Relaxed boost as safety net Wanpeng Li
2026-01-04 2:40 ` [PATCH v2 0/9] sched/kvm: Semantics-aware vCPU scheduling for oversubscribed KVM Wanpeng Li
2026-01-05 6:26 ` K Prateek Nayak
2026-03-13 1:13 ` Sean Christopherson
2026-04-01 9:48 ` Wanpeng Li
2026-04-02 23:43 ` Sean Christopherson
2026-03-26 14:41 ` Christian Borntraeger
2026-04-01 9:34 ` Wanpeng Li
2026-04-08 9:35 ` Richie Buturla
2026-04-17 11:30 ` Richie Buturla
2026-05-13 12:52 ` Richie Buturla
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=202512230415.0RatyaQF-lkp@intel.com \
--to=lkp@intel.com \
--cc=borntraeger@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kprateek.nayak@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=wanpengli@tencent.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 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.