From: kernel test robot <lkp@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/2] KVM: remove CONFIG_KVM_GENERIC_MMU_NOTIFIER
Date: Fri, 13 Feb 2026 04:05:56 +0800 [thread overview]
Message-ID: <202602130416.oIONAEUp-lkp@intel.com> (raw)
In-Reply-To: <20260212105211.1555876-2-pbonzini@redhat.com>
Hi Paolo,
kernel test robot noticed the following build errors:
[auto build test ERROR on kvm/queue]
[also build test ERROR on kvm/next kvms390/next next-20260212]
[cannot apply to powerpc/topic/ppc-kvm kvmarm/next linus/master kvm/linux-next v6.19]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Paolo-Bonzini/KVM-remove-CONFIG_KVM_GENERIC_MMU_NOTIFIER/20260212-185546
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link: https://lore.kernel.org/r/20260212105211.1555876-2-pbonzini%40redhat.com
patch subject: [PATCH 1/2] KVM: remove CONFIG_KVM_GENERIC_MMU_NOTIFIER
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20260213/202602130416.oIONAEUp-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260213/202602130416.oIONAEUp-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/202602130416.oIONAEUp-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kvm/../../../virt/kvm/kvm_main.c:900:9: error: call to undeclared function 'mmu_notifier_register'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
900 | return mmu_notifier_register(&kvm->mmu_notifier, current->mm);
| ^
arch/riscv/kvm/../../../virt/kvm/kvm_main.c:900:9: note: did you mean 'mmu_notifier_release'?
include/linux/mmu_notifier.h:598:20: note: 'mmu_notifier_release' declared here
598 | static inline void mmu_notifier_release(struct mm_struct *mm)
| ^
>> arch/riscv/kvm/../../../virt/kvm/kvm_main.c:1220:3: error: call to undeclared function 'mmu_notifier_unregister'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1220 | mmu_notifier_unregister(&kvm->mmu_notifier, current->mm);
| ^
arch/riscv/kvm/../../../virt/kvm/kvm_main.c:1220:3: note: did you mean 'preempt_notifier_unregister'?
include/linux/preempt.h:357:6: note: 'preempt_notifier_unregister' declared here
357 | void preempt_notifier_unregister(struct preempt_notifier *notifier);
| ^
arch/riscv/kvm/../../../virt/kvm/kvm_main.c:1283:2: error: call to undeclared function 'mmu_notifier_unregister'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1283 | mmu_notifier_unregister(&kvm->mmu_notifier, kvm->mm);
| ^
3 errors generated.
vim +/mmu_notifier_register +900 arch/riscv/kvm/../../../virt/kvm/kvm_main.c
4c07b0a4b6df45 Avi Kivity 2009-12-20 896
4c07b0a4b6df45 Avi Kivity 2009-12-20 897 static int kvm_init_mmu_notifier(struct kvm *kvm)
4c07b0a4b6df45 Avi Kivity 2009-12-20 898 {
4c07b0a4b6df45 Avi Kivity 2009-12-20 899 kvm->mmu_notifier.ops = &kvm_mmu_notifier_ops;
4c07b0a4b6df45 Avi Kivity 2009-12-20 @900 return mmu_notifier_register(&kvm->mmu_notifier, current->mm);
4c07b0a4b6df45 Avi Kivity 2009-12-20 901 }
4c07b0a4b6df45 Avi Kivity 2009-12-20 902
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-12 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 10:52 [PATCH 0/2] KVM: require generic MMU notifier implementation Paolo Bonzini
2026-02-12 10:52 ` [PATCH 1/2] KVM: remove CONFIG_KVM_GENERIC_MMU_NOTIFIER Paolo Bonzini
2026-02-12 17:16 ` kernel test robot
2026-02-12 18:00 ` kernel test robot
2026-02-12 20:05 ` kernel test robot [this message]
2026-02-12 10:52 ` [PATCH 2/2] KVM: always define KVM_CAP_SYNC_MMU Paolo Bonzini
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=202602130416.oIONAEUp-lkp@intel.com \
--to=lkp@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.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 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.