From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 1/2] Prevent CFS from ignoring boost requests from KVM
Date: Thu, 22 Apr 2021 02:42:31 +0800 [thread overview]
Message-ID: <202104220224.Aj4y69pg-lkp@intel.com> (raw)
In-Reply-To: <20210421150831.60133-2-kentaishiguro@sslab.ics.keio.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 8688 bytes --]
Hi Kenta,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/sched/core]
[also build test WARNING on linux/master linus/master v5.12-rc8 next-20210421]
[cannot apply to kvm/queue]
[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]
url: https://github.com/0day-ci/linux/commits/Kenta-Ishiguro/Mitigating-Excessive-Pause-Loop-Exiting-in-VM-Agnostic-KVM/20210421-234914
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 3f5ad91488e813026f8c5f46b839e91a83912703
config: x86_64-randconfig-s022-20210421 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/b803c1316e4fd9a6781869b66566f28bef3c97f4
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Kenta-Ishiguro/Mitigating-Excessive-Pause-Loop-Exiting-in-VM-Agnostic-KVM/20210421-234914
git checkout b803c1316e4fd9a6781869b66566f28bef3c97f4
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
kernel/sched/fair.c:876:34: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct sched_entity *se @@ got struct sched_entity [noderef] __rcu * @@
kernel/sched/fair.c:876:34: sparse: expected struct sched_entity *se
kernel/sched/fair.c:876:34: sparse: got struct sched_entity [noderef] __rcu *
kernel/sched/fair.c:10662: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:10662:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:10662:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:4931:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/fair.c:4931:22: sparse: struct task_struct [noderef] __rcu *
kernel/sched/fair.c:4931:22: sparse: struct task_struct *
kernel/sched/fair.c:5454:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *curr @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:5454:38: sparse: expected struct task_struct *curr
kernel/sched/fair.c:5454:38: sparse: got struct task_struct [noderef] __rcu *curr
kernel/sched/fair.c:6680: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:6680:20: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:6680:20: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:6802: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:6802:9: sparse: expected struct sched_domain *[assigned] tmp
kernel/sched/fair.c:6802:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:7000:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *curr @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:7000:38: sparse: expected struct task_struct *curr
kernel/sched/fair.c:7000:38: sparse: got struct task_struct [noderef] __rcu *curr
kernel/sched/fair.c:7251:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct task_struct *curr @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:7251:38: sparse: expected struct task_struct *curr
kernel/sched/fair.c:7251:38: sparse: got struct task_struct [noderef] __rcu *curr
>> kernel/sched/fair.c:7318:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct task_struct *curr @@ got struct task_struct [noderef] __rcu *curr @@
kernel/sched/fair.c:7318:14: sparse: expected struct task_struct *curr
kernel/sched/fair.c:7318:14: sparse: got struct task_struct [noderef] __rcu *curr
kernel/sched/fair.c:8276: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:8276:40: sparse: expected struct sched_domain *child
kernel/sched/fair.c:8276:40: sparse: got struct sched_domain [noderef] __rcu *child
kernel/sched/fair.c:8724:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/fair.c:8724:22: sparse: struct task_struct [noderef] __rcu *
kernel/sched/fair.c:8724:22: sparse: struct task_struct *
kernel/sched/fair.c:9984: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:9984:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:9984:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:9643: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:9643:44: sparse: expected struct sched_domain *sd_parent
kernel/sched/fair.c:9643:44: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:10056: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:10056:9: sparse: expected struct sched_domain *[assigned] sd
kernel/sched/fair.c:10056:9: sparse: got struct sched_domain [noderef] __rcu *parent
kernel/sched/fair.c:4599:31: sparse: sparse: marked inline, but without a definition
kernel/sched/fair.c: note: in included file:
kernel/sched/sched.h:1729:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:1729:25: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:1729:25: sparse: struct task_struct *
kernel/sched/sched.h:1884:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:1884:9: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:1884:9: sparse: struct task_struct *
kernel/sched/sched.h:1729:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:1729:25: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:1729:25: sparse: struct task_struct *
kernel/sched/sched.h:1729:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/sched.h:1729:25: sparse: struct task_struct [noderef] __rcu *
kernel/sched/sched.h:1729:25: sparse: struct task_struct *
vim +7318 kernel/sched/fair.c
7304
7305 static bool yield_to_task_fair(struct rq *rq, struct task_struct *p)
7306 {
7307 struct sched_entity *se = &p->se;
7308 struct task_struct *curr;
7309 struct sched_entity *yield_se;
7310
7311 /* throttled hierarchies are not runnable */
7312 if (!se->on_rq || throttled_hierarchy(cfs_rq_of(se)))
7313 return false;
7314
7315 /* Tell the scheduler that we'd really like pse to run next. */
7316 set_next_buddy(se);
7317
> 7318 curr = rq->curr;
7319 yield_se = &curr->se;
7320 deboost_yield_task(se, yield_se);
7321
7322 yield_task_fair(rq);
7323
7324 return true;
7325 }
7326
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 36879 bytes --]
next prev parent reply other threads:[~2021-04-21 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 15:08 [RFC PATCH 0/2] Mitigating Excessive Pause-Loop Exiting in VM-Agnostic KVM Kenta Ishiguro
2021-04-21 15:08 ` [RFC PATCH 1/2] Prevent CFS from ignoring boost requests from KVM Kenta Ishiguro
2021-04-21 18:42 ` kernel test robot [this message]
2021-04-21 15:08 ` [RFC PATCH 2/2] Boost vCPUs based on IPI-sender and receiver information Kenta Ishiguro
2021-04-21 15:43 ` Sean Christopherson
2021-04-21 16:16 ` Sean Christopherson
2021-04-21 16:19 ` [RFC PATCH 0/2] Mitigating Excessive Pause-Loop Exiting in VM-Agnostic KVM Sean Christopherson
2021-04-22 12:21 ` Wanpeng Li
2021-04-22 15:58 ` Sean Christopherson
[not found] ` <CAOOWTGJvFB_hgSUzaqNaNigdkRXFcaK37F9V7kmL3nCG+bFz5Q@mail.gmail.com>
2021-04-26 3:02 ` Wanpeng Li
2021-04-26 3:18 ` Kenta Ishiguro
2021-04-26 3:58 ` Wanpeng Li
2021-04-26 4:10 ` Kenta Ishiguro
2021-04-22 0:55 ` Wanpeng Li
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=202104220224.Aj4y69pg-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.