From: kernel test robot <lkp@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [broonie-ci:kvm-arm64-sme 17/26] arch/arm64/kvm/guest.c:325:7: error: implicit declaration of function 'vq_available' is invalid in C99
Date: Wed, 6 Dec 2023 09:21:32 +0800 [thread overview]
Message-ID: <202312060901.mfYwvqW7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git kvm-arm64-sme
head: cf8673c4f464f79c9b5528a6ca24001cb40e5605
commit: 9188453af24188b2be6a6129e4a70868fbbfc1f0 [17/26] KVM: arm64: Implement SME vector length configuration
config: arm64-randconfig-003-20231202 (https://download.01.org/0day-ci/archive/20231206/202312060901.mfYwvqW7-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312060901.mfYwvqW7-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/202312060901.mfYwvqW7-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/arm64/kvm/guest.c:325:7: error: implicit declaration of function 'vq_available' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
if (vq_available(vec_type, vq))
^
arch/arm64/kvm/guest.c:325:7: note: did you mean 'sve_vq_available'?
arch/arm64/include/asm/fpsimd.h:332:20: note: 'sve_vq_available' declared here
static inline bool sve_vq_available(unsigned int vq) { return false; }
^
arch/arm64/kvm/guest.c:365:30: error: implicit declaration of function 'vq_available' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
if (vq_present(vqs, vq) != vq_available(vec_type, vq))
^
2 errors generated.
vim +/vq_available +325 arch/arm64/kvm/guest.c
311
312 static int get_vec_vls(enum vec_type vec_type, struct kvm_vcpu *vcpu,
313 const struct kvm_one_reg *reg)
314 {
315 unsigned int max_vq, vq;
316 u64 vqs[KVM_ARM64_SVE_VLS_WORDS];
317
318 if (WARN_ON(!sve_vl_valid(vcpu->arch.max_vl[vec_type])))
319 return -EINVAL;
320
321 memset(vqs, 0, sizeof(vqs));
322
323 max_vq = vcpu_vec_max_vq(vec_type, vcpu);
324 for (vq = SVE_VQ_MIN; vq <= max_vq; ++vq)
> 325 if (vq_available(vec_type, vq))
326 vqs[vq_word(vq)] |= vq_mask(vq);
327
328 if (copy_to_user((void __user *)reg->addr, vqs, sizeof(vqs)))
329 return -EFAULT;
330
331 return 0;
332 }
333
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-06 1:22 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=202312060901.mfYwvqW7-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox