From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2] mm: hugetlb: optionally allocate gigantic hugepages using cma
Date: Tue, 10 Mar 2020 13:39:45 +0800 [thread overview]
Message-ID: <202003101351.SejHTUDy%lkp@intel.com> (raw)
In-Reply-To: <20200310002524.2291595-1-guro@fb.com>
[-- Attachment #1: Type: text/plain, Size: 5179 bytes --]
Hi Roman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.6-rc5 next-20200306]
[cannot apply to mmotm/master tip/x86/core linux/master]
[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/Roman-Gushchin/mm-hugetlb-optionally-allocate-gigantic-hugepages-using-cma/20200310-082721
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 30bb5572ce7a8710fa9ea720b6ecb382791c9800
config: x86_64-randconfig-s2-20200310 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86/kernel/setup.c: In function 'setup_arch':
>> arch/x86/kernel/setup.c:1162:2: error: implicit declaration of function 'hugetlb_cma_reserve' [-Werror=implicit-function-declaration]
hugetlb_cma_reserve();
^
cc1: some warnings being treated as errors
vim +/hugetlb_cma_reserve +1162 arch/x86/kernel/setup.c
1094
1095 reserve_real_mode();
1096
1097 trim_platform_memory_ranges();
1098 trim_low_memory_range();
1099
1100 init_mem_mapping();
1101
1102 idt_setup_early_pf();
1103
1104 /*
1105 * Update mmu_cr4_features (and, indirectly, trampoline_cr4_features)
1106 * with the current CR4 value. This may not be necessary, but
1107 * auditing all the early-boot CR4 manipulation would be needed to
1108 * rule it out.
1109 *
1110 * Mask off features that don't work outside long mode (just
1111 * PCIDE for now).
1112 */
1113 mmu_cr4_features = __read_cr4() & ~X86_CR4_PCIDE;
1114
1115 memblock_set_current_limit(get_max_mapped());
1116
1117 /*
1118 * NOTE: On x86-32, only from this point on, fixmaps are ready for use.
1119 */
1120
1121 #ifdef CONFIG_PROVIDE_OHCI1394_DMA_INIT
1122 if (init_ohci1394_dma_early)
1123 init_ohci1394_dma_on_all_controllers();
1124 #endif
1125 /* Allocate bigger log buffer */
1126 setup_log_buf(1);
1127
1128 if (efi_enabled(EFI_BOOT)) {
1129 switch (boot_params.secure_boot) {
1130 case efi_secureboot_mode_disabled:
1131 pr_info("Secure boot disabled\n");
1132 break;
1133 case efi_secureboot_mode_enabled:
1134 pr_info("Secure boot enabled\n");
1135 break;
1136 default:
1137 pr_info("Secure boot could not be determined\n");
1138 break;
1139 }
1140 }
1141
1142 reserve_initrd();
1143
1144 acpi_table_upgrade();
1145
1146 vsmp_init();
1147
1148 io_delay_init();
1149
1150 early_platform_quirks();
1151
1152 /*
1153 * Parse the ACPI tables for possible boot-time SMP configuration.
1154 */
1155 acpi_boot_table_init();
1156
1157 early_acpi_boot_init();
1158
1159 initmem_init();
1160 dma_contiguous_reserve(max_pfn_mapped << PAGE_SHIFT);
1161
> 1162 hugetlb_cma_reserve();
1163
1164 /*
1165 * Reserve memory for crash kernel after SRAT is parsed so that it
1166 * won't consume hotpluggable memory.
1167 */
1168 reserve_crashkernel();
1169
1170 memblock_find_dma_reserve();
1171
1172 if (!early_xdbc_setup_hardware())
1173 early_xdbc_register_console();
1174
1175 x86_init.paging.pagetable_init();
1176
1177 kasan_init();
1178
1179 /*
1180 * Sync back kernel address range.
1181 *
1182 * FIXME: Can the later sync in setup_cpu_entry_areas() replace
1183 * this call?
1184 */
1185 sync_initial_page_table();
1186
1187 tboot_probe();
1188
1189 map_vsyscall();
1190
1191 generic_apic_probe();
1192
1193 early_quirks();
1194
1195 /*
1196 * Read APIC and some other early information from ACPI tables.
1197 */
1198 acpi_boot_init();
1199 sfi_init();
1200 x86_dtb_init();
1201
1202 /*
1203 * get boot-time SMP configuration:
1204 */
1205 get_smp_config();
1206
1207 /*
1208 * Systems w/o ACPI and mptables might not have it mapped the local
1209 * APIC yet, but prefill_possible_map() might need to access it.
1210 */
1211 init_apic_mappings();
1212
1213 prefill_possible_map();
1214
1215 init_cpu_to_node();
1216
1217 io_apic_init_mappings();
1218
1219 x86_init.hyper.guest_late_init();
1220
1221 e820__reserve_resources();
1222 e820__register_nosave_regions(max_pfn);
1223
1224 x86_init.resources.reserve_resources();
1225
1226 e820__setup_pci_gap();
1227
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 36810 bytes --]
next prev parent reply other threads:[~2020-03-10 5:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 0:25 [PATCH v2] mm: hugetlb: optionally allocate gigantic hugepages using cma Roman Gushchin
2020-03-10 0:30 ` Roman Gushchin
2020-03-10 5:39 ` kbuild test robot [this message]
2020-03-10 8:45 ` Michal Hocko
2020-03-10 17:25 ` Roman Gushchin
2020-03-10 17:37 ` Michal Hocko
2020-03-16 1:08 ` Rik van Riel
2020-03-10 17:38 ` Mike Kravetz
2020-03-10 17:42 ` Michal Hocko
2020-03-10 9:01 ` Michal Hocko
2020-03-10 17:30 ` Roman Gushchin
2020-03-10 17:39 ` Michal Hocko
2020-03-10 17:58 ` Roman Gushchin
2020-03-10 17:27 ` Mike Kravetz
2020-03-10 18:05 ` Roman Gushchin
2020-03-10 18:22 ` Rik van Riel
2020-03-10 18:33 ` Mike Kravetz
2020-03-10 18:54 ` Andreas Schaufler
2020-03-10 18:56 ` Roman Gushchin
2020-03-10 19:00 ` Andreas Schaufler
2020-03-10 19:19 ` Roman Gushchin
2020-03-10 19:36 ` Michal Hocko
2020-03-10 19:46 ` Rik van Riel
2020-03-10 20:11 ` Mike Kravetz
2020-03-10 20:15 ` Rik van Riel
2020-03-10 20:29 ` Mike Kravetz
2020-03-10 20:38 ` Rik van Riel
2020-03-10 20:29 ` Roman Gushchin
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=202003101351.SejHTUDy%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.