Re: [kvm:queue 11/44] arch/x86/kernel/kvm.c:672:2: error: implicit declaration of function 'kvm_guest_cpu_offline'; did you mean 'kvm_guest_cpu_init'?

[Vitaly Kuznetsov <vkuznets@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

kernel test robot <lkp@intel.com> writes:

> tree:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> head:   c6d517aecd40b25ea05c593962b2c4b085092343
> commit: 9140e381e0f2f8cb1c628c29730ece2a52cb4cbc [11/44] x86/kvm: Teardown PV features on boot CPU as well
> config: x86_64-randconfig-c022-20210506 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
>         # https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?id=9140e381e0f2f8cb1c628c29730ece2a52cb4cbc
>         git remote add kvm https://git.kernel.org/pub/scm/virt/kvm/kvm.git
>         git fetch --no-tags kvm queue
>         git checkout 9140e381e0f2f8cb1c628c29730ece2a52cb4cbc
>         # save the attached .config to linux build tree
>         make W=1 W=1 ARCH=x86_64 
>
> 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/x86/kernel/kvm.c: In function 'kvm_suspend':
>>> arch/x86/kernel/kvm.c:672:2: error: implicit declaration of function 'kvm_guest_cpu_offline'; did you mean 'kvm_guest_cpu_init'? [-Werror=implicit-function-declaration]
>      672 |  kvm_guest_cpu_offline();
>          |  ^~~~~~~~~~~~~~~~~~~~~
>          |  kvm_guest_cpu_init
>    arch/x86/kernel/kvm.c: In function 'kvm_resume':
>>> arch/x86/kernel/kvm.c:679:2: error: implicit declaration of function 'kvm_cpu_online'; did you mean 'irq_cpu_online'? [-Werror=implicit-function-declaration]
>      679 |  kvm_cpu_online(raw_smp_processor_id());
>          |  ^~~~~~~~~~~~~~
>          |  irq_cpu_online
>    cc1: some warnings being treated as errors
>


Oh well, we just need a quantum PC and something like 
'make allpossibleconfig' to make issues like this one go away forever
:-)

I'm on it, soemthing needs to be done for !CONFIG_SMP case.


-- 
Vitaly