linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: kbuild-all@lists.01.org,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Barry Song <song.bao.hua@hisilicon.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/hugetlb: Reserve CMA areas for gigantic pages on 16K and 64K configs
Date: Tue, 23 Jun 2020 17:24:48 +0800	[thread overview]
Message-ID: <202006231703.DC6xDVaw%lkp@intel.com> (raw)
In-Reply-To: <1592893296-22040-1-git-send-email-anshuman.khandual@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]

Hi Anshuman,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v5.8-rc2]
[also build test ERROR on next-20200623]
[cannot apply to arm64/for-next/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Anshuman-Khandual/arm64-hugetlb-Reserve-CMA-areas-for-gigantic-pages-on-16K-and-64K-configs/20200623-142507
base:    48778464bb7d346b47157d21ffde2af6b2d39110
config: arm64-allnoconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
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
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/arm64/mm/init.c: In function 'bootmem_init':
>> arch/arm64/mm/init.c:428:2: error: implicit declaration of function 'arm64_hugetlb_cma_reserve'; did you mean 'hugetlb_cma_reserve'? [-Werror=implicit-function-declaration]
     428 |  arm64_hugetlb_cma_reserve();
         |  ^~~~~~~~~~~~~~~~~~~~~~~~~
         |  hugetlb_cma_reserve
   cc1: some warnings being treated as errors

vim +428 arch/arm64/mm/init.c

   408	
   409	void __init bootmem_init(void)
   410	{
   411		unsigned long min, max;
   412	
   413		min = PFN_UP(memblock_start_of_DRAM());
   414		max = PFN_DOWN(memblock_end_of_DRAM());
   415	
   416		early_memtest(min << PAGE_SHIFT, max << PAGE_SHIFT);
   417	
   418		max_pfn = max_low_pfn = max;
   419		min_low_pfn = min;
   420	
   421		arm64_numa_init();
   422	
   423		/*
   424		 * must be done after arm64_numa_init() which calls numa_init() to
   425		 * initialize node_online_map that gets used in hugetlb_cma_reserve()
   426		 * while allocating required CMA size across online nodes.
   427		 */
 > 428		arm64_hugetlb_cma_reserve();
   429	
   430		/*
   431		 * Sparsemem tries to allocate bootmem in memory_present(), so must be
   432		 * done after the fixed reservations.
   433		 */
   434		memblocks_present();
   435	
   436		sparse_init();
   437		zone_sizes_init(min, max);
   438	
   439		memblock_dump_all();
   440	}
   441	

---
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: 8161 bytes --]

  reply	other threads:[~2020-06-23  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  6:21 [PATCH] arm64/hugetlb: Reserve CMA areas for gigantic pages on 16K and 64K configs Anshuman Khandual
2020-06-23  9:24 ` kernel test robot [this message]
2020-06-23 12:48   ` Anshuman Khandual
2020-06-23 16:40     ` Robin Murphy
2020-06-24  0:17       ` Anshuman Khandual
2020-06-24  9:45         ` Robin Murphy
2020-06-24 12:22           ` Anshuman Khandual
2020-06-26 18:42 ` kernel test robot

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=202006231703.DC6xDVaw%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.kravetz@oracle.com \
    --cc=song.bao.hua@hisilicon.com \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).