From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [sean-jc:x86/kill_should_kick_with_force 3/7] arch/powerpc/kvm/powerpc.c:1906:9: error: implicit declaration of function 'kvmppc_vcpu_kick'; did you mean 'kvm_vcpu_kick'?
Date: Fri, 16 Oct 2026 00:59:45 +0800 [thread overview]
Message-ID: <202610160007.HMCCMTIp-lkp@intel.com> (raw)
tree: https://github.com/sean-jc/linux x86/kill_should_kick_with_force
head: 01d71338eb030f22b384bb16b117a6429b0ed13a
commit: 9be4d75f5b9b7cb22aa41ed3b0d1e8b8fa5335e8 [3/7] KVM: PPC: Explicitly force IPIs when directly kicking vCPUs
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20261016/202610160007.HMCCMTIp-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261016/202610160007.HMCCMTIp-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/202610160007.HMCCMTIp-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/powerpc/kvm/powerpc.c: In function 'kvm_vcpu_ioctl_interrupt':
>> arch/powerpc/kvm/powerpc.c:1906:9: error: implicit declaration of function 'kvmppc_vcpu_kick'; did you mean 'kvm_vcpu_kick'? [-Wimplicit-function-declaration]
1906 | kvmppc_vcpu_kick(vcpu);
| ^~~~~~~~~~~~~~~~
| kvm_vcpu_kick
--
arch/powerpc/kvm/book3s.c: In function 'kvmppc_decrementer_func':
>> arch/powerpc/kvm/book3s.c:830:9: error: implicit declaration of function 'kvmppc_vcpu_kick'; did you mean 'kvm_vcpu_kick'? [-Wimplicit-function-declaration]
830 | kvmppc_vcpu_kick(vcpu);
| ^~~~~~~~~~~~~~~~
| kvm_vcpu_kick
--
>> arch/powerpc/kvm/book3s_pr.c:2069:27: error: 'kvmppc_vcpu_kick' undeclared here (not in a function); did you mean 'kvm_vcpu_kick'?
2069 | .fast_vcpu_kick = kvmppc_vcpu_kick,
| ^~~~~~~~~~~~~~~~
| kvm_vcpu_kick
vim +1906 arch/powerpc/kvm/powerpc.c
1896
1897 int kvm_vcpu_ioctl_interrupt(struct kvm_vcpu *vcpu, struct kvm_interrupt *irq)
1898 {
1899 if (irq->irq == KVM_INTERRUPT_UNSET) {
1900 kvmppc_core_dequeue_external(vcpu);
1901 return 0;
1902 }
1903
1904 kvmppc_core_queue_external(vcpu, irq);
1905
> 1906 kvmppc_vcpu_kick(vcpu);
1907
1908 return 0;
1909 }
1910
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-15 17:00 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=202610160007.HMCCMTIp-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@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 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.