Hello Paolo, On Thu, Feb 17, 2022 at 8:13 PM kernel test robot <lkp@xxxxxxxxx> wrote: > > tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git master > head: 988896bb61827345c6d074dd5f2af1b7b008193f > commit: 988896bb61827345c6d074dd5f2af1b7b008193f [22/22] x86/kvm/fpu: Remove kvm_vcpu_arch.guest_supported_xcr0 > config: i386-randconfig-a002 (https://download.01.org/0day-ci/archive/20220218/202202180700.dnGoHs4Z-lkp@xxxxxxxxx/config) > compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e) > 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 > # https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?id=988896bb61827345c6d074dd5f2af1b7b008193f > git remote add kvm https://git.kernel.org/pub/scm/virt/kvm/kvm.git > git fetch --no-tags kvm master > git checkout 988896bb61827345c6d074dd5f2af1b7b008193f > # save the config file to linux build tree > mkdir build_dir > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash > > If you fix the issue, kindly add following tag as appropriate > Reported-by: kernel test robot <lkp@xxxxxxxxx> > > All errors (new ones prefixed by >>): > > >> arch/x86/kvm/x86.c:992:19: error: unused function 'kvm_guest_supported_xfd' [-Werror,-Wunused-function] > static inline u64 kvm_guest_supported_xfd(struct kvm_vcpu *vcpu) It seems to fail under "non-x86_64" x86 configs, since kvm_guest_supported_xfd() is called only in x86_64 code. I will send a new version for this patchset only, incorporating the ifdefs in this function. Rationale: If MSR_IA32_XFD and MSR_IA32_XFD_ERR are in x86_64-only code, it only makes sense that XFD is an x86_64 only feature. > ^ > arch/x86/kvm/x86.c:2364:19: error: unused function 'gtod_is_based_on_tsc' [-Werror,-Wunused-function] > static inline int gtod_is_based_on_tsc(int mode) > ^ > 2 errors generated. The same thing happens for this one (which is unrelated to my patchset), but will require the same fix. I will send an additional patch fixing this one also. Is that ok? Best regards, Leo
