From: kernel test robot <lkp@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Will Deacon <will@kernel.org>
Subject: [linux-next:master 9605/11937] arch/arm64/kvm/reset.c:49:20: error: implicit declaration of function 'sve_max_virtualisable_vl'
Date: Wed, 27 Oct 2021 23:23:00 +0800 [thread overview]
Message-ID: <202110272350.XOrJFVKE-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3037 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ae5179317e794160e471db0e122c6ac811a97235
commit: b5bc00ffddc08c20a799514cbcfd2abaa6718014 [9605/11937] arm64/sve: Put system wide vector length information into structs
config: arm64-randconfig-r033-20211027 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 5db7568a6a1fcb408eb8988abdaff2a225a8eb72)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b5bc00ffddc08c20a799514cbcfd2abaa6718014
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout b5bc00ffddc08c20a799514cbcfd2abaa6718014
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD ae5179317e794160e471db0e122c6ac811a97235 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> arch/arm64/kvm/reset.c:49:20: error: implicit declaration of function 'sve_max_virtualisable_vl' [-Werror,-Wimplicit-function-declaration]
kvm_sve_max_vl = sve_max_virtualisable_vl();
^
arch/arm64/kvm/reset.c:105:40: error: implicit declaration of function 'sve_max_virtualisable_vl' [-Werror,-Wimplicit-function-declaration]
if (WARN_ON(!sve_vl_valid(vl) || vl > sve_max_virtualisable_vl() ||
^
2 errors generated.
vim +/sve_max_virtualisable_vl +49 arch/arm64/kvm/reset.c
45
46 int kvm_arm_init_sve(void)
47 {
48 if (system_supports_sve()) {
> 49 kvm_sve_max_vl = sve_max_virtualisable_vl();
50
51 /*
52 * The get_sve_reg()/set_sve_reg() ioctl interface will need
53 * to be extended with multiple register slice support in
54 * order to support vector lengths greater than
55 * SVE_VL_ARCH_MAX:
56 */
57 if (WARN_ON(kvm_sve_max_vl > SVE_VL_ARCH_MAX))
58 kvm_sve_max_vl = SVE_VL_ARCH_MAX;
59
60 /*
61 * Don't even try to make use of vector lengths that
62 * aren't available on all CPUs, for now:
63 */
64 if (kvm_sve_max_vl < sve_max_vl())
65 pr_warn("KVM: SVE vector length for guests limited to %u bytes\n",
66 kvm_sve_max_vl);
67 }
68
69 return 0;
70 }
71
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45135 bytes --]
reply other threads:[~2021-10-27 15:23 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=202110272350.XOrJFVKE-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).