From: kbuild test robot <lkp@intel.com>
To: Huaixin Chang <changhuaixin@linux.alibaba.com>,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, peterz@infradead.org, mingo@redhat.com,
bsegall@google.com, chiluk+linux@indeed.com,
vincent.guittot@linaro.org, pauld@redhead.com,
Huaixin Chang <changhuaixin@linux.alibaba.com>
Subject: Re: [PATCH 1/2] sched: Defend cfs and rt bandwidth quota against overflow
Date: Fri, 24 Apr 2020 14:35:16 +0800 [thread overview]
Message-ID: <202004241458.Z5hytr2T%lkp@intel.com> (raw)
In-Reply-To: <20200420024421.22442-2-changhuaixin@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
Hi Huaixin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on tip/auto-latest linus/master v5.7-rc2 next-20200423]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Huaixin-Chang/Two-small-fixes-for-bandwidth-controller/20200421-230027
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 8f3d9f354286745c751374f5f1fcafee6b3f3136
config: i386-randconfig-a001-20200424 (attached as .config)
compiler: gcc-4.9 (Ubuntu 4.9.3-13ubuntu2) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
>> kernel/sched/core.c:7394:1: warning: left shift count >= width of type
static const u64 max_cfs_runtime = MAX_BW_USEC * NSEC_PER_USEC;
^
>> kernel/sched/core.c:7394:1: error: initializer element is not computable at load time
vim +7394 kernel/sched/core.c
7390
7391 const u64 max_cfs_quota_period = 1 * NSEC_PER_SEC; /* 1s */
7392 static const u64 min_cfs_quota_period = 1 * NSEC_PER_MSEC; /* 1ms */
7393 /* More than 203 days if BW_SHIFT equals 20. */
> 7394 static const u64 max_cfs_runtime = MAX_BW_USEC * NSEC_PER_USEC;
7395
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35519 bytes --]
next prev parent reply other threads:[~2020-04-24 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 2:44 [PATCH 0/2] Two small fixes for bandwidth controller Huaixin Chang
2020-04-20 2:44 ` [PATCH 1/2] sched: Defend cfs and rt bandwidth quota against overflow Huaixin Chang
2020-04-20 17:50 ` bsegall
2020-04-22 3:36 ` changhuaixin
2020-04-22 18:44 ` bsegall
2020-04-23 13:37 ` [PATCH] " Huaixin Chang
2020-04-23 20:33 ` bsegall
2020-04-25 10:52 ` [PATCH v2] " Huaixin Chang
2020-04-27 18:29 ` bsegall
2020-05-11 13:03 ` Peter Zijlstra
2020-05-19 18:44 ` [tip: sched/core] " tip-bot2 for Huaixin Chang
2020-04-22 8:38 ` [PATCH 1/2] " kbuild test robot
2020-04-24 6:35 ` kbuild test robot [this message]
2020-04-20 2:44 ` [PATCH 2/2] sched/fair: Refill bandwidth before scaling Huaixin Chang
2020-04-20 17:54 ` bsegall
2020-04-21 15:09 ` Phil Auld
2020-05-01 18:22 ` [tip: sched/core] " tip-bot2 for Huaixin Chang
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=202004241458.Z5hytr2T%lkp@intel.com \
--to=lkp@intel.com \
--cc=bsegall@google.com \
--cc=changhuaixin@linux.alibaba.com \
--cc=chiluk+linux@indeed.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pauld@redhead.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome