From: kernel test robot <lkp@intel.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Anup Patel <anup@brainfault.org>
Subject: [linux-next:master 14077/15065] arch/riscv/mm/ptdump.c:383:53: error: use of undeclared identifier 'kernel_virt_addr'
Date: Tue, 27 Apr 2021 12:19:10 +0800 [thread overview]
Message-ID: <202104271201.ezZDFT0p-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3499 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3f1fee3e7237347f09a2c7fa538119e6d9ea4b84
commit: 9d48716fc5fda7f610c70104b5fef60eb55a4ab3 [14077/15065] riscv: Prepare ptdump for vm layout dynamic addresses
config: riscv-randconfig-r032-20210426 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d7308da4a5aaded897a7e0c06e7e88d81fc64879)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9d48716fc5fda7f610c70104b5fef60eb55a4ab3
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 9d48716fc5fda7f610c70104b5fef60eb55a4ab3
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=riscv
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/riscv/mm/ptdump.c:383:53: error: use of undeclared identifier 'kernel_virt_addr'
address_markers[KERNEL_MAPPING_NR].start_address = kernel_virt_addr;
^
1 error generated.
vim +/kernel_virt_addr +383 arch/riscv/mm/ptdump.c
360
361 static int ptdump_init(void)
362 {
363 unsigned int i, j;
364
365 #ifdef CONFIG_KASAN
366 address_markers[KASAN_SHADOW_START_NR].start_address = KASAN_SHADOW_START;
367 address_markers[KASAN_SHADOW_END_NR].start_address = KASAN_SHADOW_END;
368 #endif
369 address_markers[FIXMAP_START_NR].start_address = FIXADDR_START;
370 address_markers[FIXMAP_END_NR].start_address = FIXADDR_TOP;
371 address_markers[PCI_IO_START_NR].start_address = PCI_IO_START;
372 address_markers[PCI_IO_END_NR].start_address = PCI_IO_END;
373 #ifdef CONFIG_SPARSEMEM_VMEMMAP
374 address_markers[VMEMMAP_START_NR].start_address = VMEMMAP_START;
375 address_markers[VMEMMAP_END_NR].start_address = VMEMMAP_END;
376 #endif
377 address_markers[VMALLOC_START_NR].start_address = VMALLOC_START;
378 address_markers[VMALLOC_END_NR].start_address = VMALLOC_END;
379 address_markers[PAGE_OFFSET_NR].start_address = PAGE_OFFSET;
380 #ifdef CONFIG_64BIT
381 address_markers[MODULES_MAPPING_NR].start_address = MODULES_VADDR;
382 #endif
> 383 address_markers[KERNEL_MAPPING_NR].start_address = kernel_virt_addr;
384
385 kernel_ptd_info.base_addr = KERN_VIRT_START;
386
387 for (i = 0; i < ARRAY_SIZE(pg_level); i++)
388 for (j = 0; j < ARRAY_SIZE(pte_bits); j++)
389 pg_level[i].mask |= pte_bits[j].mask;
390
391 debugfs_create_file("kernel_page_tables", 0400, NULL, &kernel_ptd_info,
392 &ptdump_fops);
393 #ifdef CONFIG_EFI
394 if (efi_enabled(EFI_RUNTIME_SERVICES))
395 debugfs_create_file("efi_page_tables", 0400, NULL, &efi_ptd_info,
396 &ptdump_fops);
397 #endif
398
399 return 0;
400 }
401
---
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: 40104 bytes --]
reply other threads:[~2021-04-27 4:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202104271201.ezZDFT0p-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=palmerdabbelt@google.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