From: kernel test robot <lkp@intel.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 11242/11394] arch/riscv/include/asm/pgtable.h:443:41: error: implicit declaration of function 'napot_cont_size'
Date: Sun, 3 Mar 2024 01:44:47 +0800 [thread overview]
Message-ID: <202403030137.l7lx0vQ2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1870cdc0e8dee32e3c221704a2977898ba4c10e8
commit: 224eb81771e34595a6472772514b36ff8c3ec9a0 [11242/11394] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
config: riscv-randconfig-r003-20230430 (https://download.01.org/0day-ci/archive/20240303/202403030137.l7lx0vQ2-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240303/202403030137.l7lx0vQ2-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403030137.l7lx0vQ2-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/riscv/include/asm/uaccess.h:12,
from include/linux/uaccess.h:11,
from include/linux/sched/task.h:13,
from include/linux/sched/signal.h:9,
from include/linux/rcuwait.h:6,
from include/linux/percpu-rwsem.h:7,
from include/linux/fs.h:33,
from kernel/events/core.c:11:
kernel/events/core.c: In function 'perf_get_pgtable_size':
>> arch/riscv/include/asm/pgtable.h:443:41: error: implicit declaration of function 'napot_cont_size' [-Werror=implicit-function-declaration]
443 | napot_cont_size(napot_cont_order(pte)) :\
| ^~~~~~~~~~~~~~~
kernel/events/core.c:7588:24: note: in expansion of macro 'pte_leaf_size'
7588 | size = pte_leaf_size(pte);
| ^~~~~~~~~~~~~
>> arch/riscv/include/asm/pgtable.h:443:57: error: implicit declaration of function 'napot_cont_order'; did you mean 'get_count_order'? [-Werror=implicit-function-declaration]
443 | napot_cont_size(napot_cont_order(pte)) :\
| ^~~~~~~~~~~~~~~~
kernel/events/core.c:7588:24: note: in expansion of macro 'pte_leaf_size'
7588 | size = pte_leaf_size(pte);
| ^~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/napot_cont_size +443 arch/riscv/include/asm/pgtable.h
9e953cda5cdf1c Alexandre Ghiti 2019-05-26 441
e0fe5ab4192c17 Alexandre Ghiti 2024-02-27 442 #define pte_leaf_size(pte) (pte_napot(pte) ? \
e0fe5ab4192c17 Alexandre Ghiti 2024-02-27 @443 napot_cont_size(napot_cont_order(pte)) :\
e0fe5ab4192c17 Alexandre Ghiti 2024-02-27 444 PAGE_SIZE)
e0fe5ab4192c17 Alexandre Ghiti 2024-02-27 445
:::::: The code at line 443 was first introduced by commit
:::::: e0fe5ab4192c171c111976dbe90bbd37d3976be0 riscv: Fix pte_leaf_size() for NAPOT
:::::: TO: Alexandre Ghiti <alexghiti@rivosinc.com>
:::::: CC: Palmer Dabbelt <palmer@rivosinc.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-02 17:45 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=202403030137.l7lx0vQ2-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.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