From: kbuild test robot <lkp@intel.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: kbuild-all@01.org, peterz@infradead.org, mingo@kernel.org,
rostedt@goodmis.org, tglx@linutronix.de, raistlin@linux.it,
linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
bristot@redhat.com, kernel-team@lge.com
Subject: Re: [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()
Date: Thu, 11 Jan 2018 01:22:08 +0800 [thread overview]
Message-ID: <201801110146.1VhAkQtt%fengguang.wu@intel.com> (raw)
In-Reply-To: <1515392095-32455-2-git-send-email-byungchul.park@lge.com>
Hi Byungchul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on v4.15-rc7 next-20180110]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Byungchul-Park/sched-deadline-Add-support-for-SD_PREFER_SIBLING-on-find_later_rq/20180110-225946
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/deadline.c:1124:5: sparse: symbol 'grub_reclaim' was not declared. Should it be
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/deadline.c:1916:9: sparse: incompatible types in comparison expression (different address spaces)
kernel/sched/sched.h:2104:16: sparse: incompatible types in comparison expression (different address spaces)
>> kernel/sched/deadline.c:1857:55: sparse: incorrect type in argument 1 (different modifiers) @@ expected struct sched_domain @@ got structstruct sched_domain @@
kernel/sched/deadline.c:1857:55: expected struct sched_domain
kernel/sched/deadline.c:1857:55: got struct sched_domain const
kernel/sched/deadline.c:1858:64: sparse: incorrect type in argument 1 (different modifiers) @@ expected struct sched_domain @@ got structstruct sched_domain @@
kernel/sched/deadline.c:1858:64: expected struct sched_domain
kernel/sched/deadline.c:1858:64: got struct sched_domain const
kernel/sched/deadline.c:563:9: sparse: context imbalance in 'dl_task_offline_migration' - unexpected unlock
kernel/sched/deadline.c:2060:9: sparse: context imbalance in 'find_lock_later_rq' - different lock contexts for basic block
kernel/sched/deadline.c:2155:23: sparse: context imbalance in 'push_dl_task' - unexpected unlock
kernel/sched/sched.h:1856:17: sparse: context imbalance in 'pull_dl_task' - unexpected unlock
kernel/sched/deadline.c: In function 'find_cpu':
kernel/sched/deadline.c:1857:48: warning: passing argument 1 of 'sched_domain_span' discards 'const' qualifier from pointer target type
const struct cpumask = sched_domain_span(sd);
^~
In file included from kernel/sched/sched.h:6:0,
from kernel/sched/deadline.c:18:
include/linux/sched/topology.h:160:31: note: expected 'struct sched_domain but argument is of type 'const struct sched_domain
static inline struct cpumask sched_domain
^~~~~~~~~~~~~~~~~
kernel/sched/deadline.c:1858:57: warning: passing argument 1 of 'sched_domain_span' discards 'const' qualifier from pointer target type
const struct cpumask = prefer sched_domain_span(prefer) : NULL;
^~~~~~
In file included from kernel/sched/sched.h:6:0,
from kernel/sched/deadline.c:18:
include/linux/sched/topology.h:160:31: note: expected 'struct sched_domain but argument is of type 'const struct sched_domain
static inline struct cpumask sched_domain
^~~~~~~~~~~~~~~~~
vim +1857 kernel/sched/deadline.c
1849
1850 /*
1851 * Find the first cpu in: mask & sd & ~prefer
1852 */
1853 static int find_cpu(const struct cpumask *mask,
1854 const struct sched_domain *sd,
1855 const struct sched_domain *prefer)
1856 {
> 1857 const struct cpumask *sds = sched_domain_span(sd);
1858 const struct cpumask *ps = prefer ? sched_domain_span(prefer) : NULL;
1859 int cpu;
1860
1861 for_each_cpu(cpu, mask) {
1862 if (!cpumask_test_cpu(cpu, sds))
1863 continue;
1864 if (ps && cpumask_test_cpu(cpu, ps))
1865 continue;
1866 break;
1867 }
1868
1869 return cpu;
1870 }
1871
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-01-10 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 6:14 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2018-01-08 6:14 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2018-01-10 17:22 ` kbuild test robot [this message]
2018-01-11 7:48 ` Byungchul Park
2018-01-08 6:14 ` [RESEND PATCH v11 2/2] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq() Byungchul Park
2018-01-10 17:45 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2018-05-09 6:44 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2018-05-09 6:44 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-12-28 23:32 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-12-28 23:32 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-12-19 1:20 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-12-19 1:20 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-11-02 1:25 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-11-02 1:25 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-10-10 6:37 [RESEND PATCH v11 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-10-10 6:37 ` [RESEND PATCH v11 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-10-23 8:44 ` Byungchul Park
2017-10-27 8:39 ` Byungchul Park
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=201801110146.1VhAkQtt%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bristot@redhat.com \
--cc=byungchul.park@lge.com \
--cc=juri.lelli@gmail.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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