From: kernel test robot <lkp@intel.com>
To: Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org, Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v6 4/8] mm,memory_hotplug: Allocate memmap from the added memory range
Date: Wed, 7 Apr 2021 01:10:35 +0800 [thread overview]
Message-ID: <202104070158.rhCTmt9u-lkp@intel.com> (raw)
In-Reply-To: <20210406111115.8953-5-osalvador@suse.de>
[-- Attachment #1: Type: text/plain, Size: 3937 bytes --]
Hi Oscar,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on pm/linux-next tip/x86/core arm64/for-next/core linus/master v5.12-rc6]
[cannot apply to hnaz-linux-mm/master next-20210406]
[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/Oscar-Salvador/Allocate-memmap-from-hotadded-memory-per-device/20210406-191333
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 6e11b376fd74356e32d842be588e12dc9bf6e197
config: x86_64-randconfig-a015-20210406 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project a46f59a747a7273cc439efaf3b4f98d8b63d2f20)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/0day-ci/linux/commit/4d4265dd4e598c7b0971d57894685136229f5d07
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Oscar-Salvador/Allocate-memmap-from-hotadded-memory-per-device/20210406-191333
git checkout 4d4265dd4e598c7b0971d57894685136229f5d07
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 >>):
>> drivers/base/memory.c:201:3: error: implicit declaration of function 'vmemmap_deinit_space' [-Werror,-Wimplicit-function-declaration]
vmemmap_deinit_space(start_pfn, nr_vmemmap_pages);
^
drivers/base/memory.c:201:3: note: did you mean 'vmemmap_init_space'?
include/linux/memory_hotplug.h:112:12: note: 'vmemmap_init_space' declared here
extern int vmemmap_init_space(unsigned long pfn, unsigned long nr_pages,
^
drivers/base/memory.c:231:4: error: implicit declaration of function 'vmemmap_deinit_space' [-Werror,-Wimplicit-function-declaration]
vmemmap_deinit_space(start_pfn, nr_pages);
^
2 errors generated.
vim +/vmemmap_deinit_space +201 drivers/base/memory.c
171
172 static int memory_block_online(struct memory_block *mem)
173 {
174 unsigned long start_pfn = section_nr_to_pfn(mem->start_section_nr);
175 unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
176 unsigned long nr_vmemmap_pages = mem->nr_vmemmap_pages;
177 int ret;
178
179 /*
180 * Although vmemmap pages have a different lifecycle than the pages
181 * they describe (they remain until the memory is unplugged), doing
182 * its initialization and accounting at hot-{online,offline} stage
183 * simplifies things a lot
184 */
185 if (nr_vmemmap_pages) {
186 ret = vmemmap_init_space(start_pfn, nr_vmemmap_pages, mem->nid,
187 mem->online_type);
188 if (ret)
189 return ret;
190 }
191
192 ret = online_pages(start_pfn + nr_vmemmap_pages,
193 nr_pages - nr_vmemmap_pages, mem->online_type,
194 mem->nid);
195
196 /*
197 * Undo the work if online_pages() fails.
198 */
199 if (ret && nr_vmemmap_pages) {
200 vmemmap_adjust_pages(start_pfn, -nr_vmemmap_pages);
> 201 vmemmap_deinit_space(start_pfn, nr_vmemmap_pages);
202 }
203
204 return ret;
205 }
206
---
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: 41796 bytes --]
next prev parent reply other threads:[~2021-04-06 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210406111115.8953-1-osalvador@suse.de>
2021-04-06 11:11 ` [PATCH v6 1/8] drivers/base/memory: Introduce memory_block_{online,offline} Oscar Salvador
2021-04-06 11:11 ` [PATCH v6 2/8] mm,memory_hotplug: Relax fully spanned sections check Oscar Salvador
2021-04-06 15:32 ` David Hildenbrand
2021-04-06 16:33 ` Oscar Salvador
2021-04-06 20:43 ` David Hildenbrand
2021-04-07 7:42 ` Oscar Salvador
2021-04-07 7:43 ` David Hildenbrand
2021-04-06 11:11 ` [PATCH v6 3/8] mm,memory_hotplug: Factor out adjusting present pages into adjust_present_page_count() Oscar Salvador
2021-04-06 15:33 ` David Hildenbrand
2021-04-07 7:11 ` Oscar Salvador
2021-04-06 11:11 ` [PATCH v6 5/8] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-04-06 11:11 ` [PATCH v6 6/8] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-04-06 11:11 ` [PATCH v6 7/8] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-04-06 11:11 ` [PATCH v6 8/8] arm64/Kconfig: " Oscar Salvador
[not found] ` <20210406111115.8953-5-osalvador@suse.de>
2021-04-06 17:10 ` kernel test robot [this message]
2021-04-06 20:28 ` [PATCH v6 4/8] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-04-07 20:38 ` Oscar Salvador
2021-04-09 5:05 ` Andrew Morton
2021-04-09 5:10 ` Oscar Salvador
2021-04-09 8:10 ` David Hildenbrand
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=202104070158.rhCTmt9u-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=david@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=vbabka@suse.cz \
/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).