Hi Mark,

FYI, the error/warning still remains.

tree: https://gitee.com/openeuler/kernel.git OLK-5.10 head: b96ea10d92add994f978118c6e3280a03a1daaf1 commit: 68da302c8ae30331c8917f1dc7b0f1682f696d71 [21144/30000] arm64/sve: Put system wide vector length information into structs config: arm64-randconfig-004-20241108 (https://download.01.org/0day-ci/archive/20241108/202411080635.2RiYCRd1-lkp@i...) compiler: aarch64-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241108/202411080635.2RiYCRd1-lkp@i...)

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/202411080635.2RiYCRd1-lkp@intel.com/

All errors (new ones prefixed by >>):

arch/arm64/kvm/reset.c: In function 'kvm_arm_init_sve':

...

arch/arm64/kvm/reset.c:102:34: error: implicit declaration of function 'sve_max_virtualisable_vl' [-Werror=implicit-function-declaration]

102 | kvm_sve_max_vl = sve_max_virtualisable_vl(); | ^~~~~~~~~~~~~~~~~~~~~~~~ cc1: some warnings being treated as errors

vim +/sve_max_virtualisable_vl +102 arch/arm64/kvm/reset.c

98 99 int kvm_arm_init_sve(void) 100 { 101 if (system_supports_sve()) {

102 kvm_sve_max_vl = sve_max_virtualisable_vl();

103 104 /* 105 * The get_sve_reg()/set_sve_reg() ioctl interface will need 106 * to be extended with multiple register slice support in 107 * order to support vector lengths greater than 108 * SVE_VL_ARCH_MAX: 109 */ 110 if (WARN_ON(kvm_sve_max_vl > SVE_VL_ARCH_MAX)) 111 kvm_sve_max_vl = SVE_VL_ARCH_MAX; 112 113 /* 114 * Don't even try to make use of vector lengths that 115 * aren't available on all CPUs, for now: 116 */ 117 if (kvm_sve_max_vl < sve_max_vl()) 118 pr_warn("KVM: SVE vector length for guests limited to %u bytes\n", 119 kvm_sve_max_vl); 120 } 121 122 return 0; 123 } 124