From: kernel test robot <lkp@intel.com>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] mm: introduce defer free for cma
Date: Fri, 7 Apr 2023 22:03:16 +0800 [thread overview]
Message-ID: <202304072120.1qQfF86Z-lkp@intel.com> (raw)
In-Reply-To: <1680864131-4675-1-git-send-email-zhaoyang.huang@unisoc.com>
Hi zhaoyang.huang,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/zhaoyang-huang/mm-introduce-defer-free-for-cma/20230407-184459
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/1680864131-4675-1-git-send-email-zhaoyang.huang%40unisoc.com
patch subject: [RFC PATCH] mm: introduce defer free for cma
config: i386-randconfig-a001-20230403 (https://download.01.org/0day-ci/archive/20230407/202304072120.1qQfF86Z-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/7abee7e8d17803e68bfff3de73df6a1dff270ff6
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review zhaoyang-huang/mm-introduce-defer-free-for-cma/20230407-184459
git checkout 7abee7e8d17803e68bfff3de73df6a1dff270ff6
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304072120.1qQfF86Z-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/cma.c:165:19: warning: operator '<<' has lower precedence than '-'; '-' will be evaluated first [-Wshift-op-parentheses]
val = cma->count - (u64)used << cma->order_per_bit;
~~~~~~~~~~~^~~~~~~~~~~ ~~
mm/cma.c:165:19: note: place parentheses around the '-' expression to silence this warning
val = cma->count - (u64)used << cma->order_per_bit;
^
( )
mm/cma.c:157:22: warning: unused function 'cma_free_get' [-Wunused-function]
static unsigned long cma_free_get(struct cma *cma)
^
2 warnings generated.
vim +165 mm/cma.c
156
157 static unsigned long cma_free_get(struct cma *cma)
158 {
159 unsigned long used;
160 unsigned long val;
161
162 spin_lock_irq(&cma->lock);
163 /* pages counter is smaller than sizeof(int) */
164 used = bitmap_weight(cma->bitmap, (int)cma_bitmap_maxno(cma));
> 165 val = cma->count - (u64)used << cma->order_per_bit;
166 spin_unlock_irq(&cma->lock);
167
168 return val;
169 }
170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
parent reply other threads:[~2023-04-07 14:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1680864131-4675-1-git-send-email-zhaoyang.huang@unisoc.com>]
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=202304072120.1qQfF86Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhaoyang.huang@unisoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox