From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 1/1] drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c:54:5: sparse: sparse: symbol 'kvm_arm_io_pgtable_init' was not declared. Should it be static?
Date: Fri, 19 Jul 2024 08:48:59 +0800 [thread overview]
Message-ID: <202407190840.0Hdo1DDB-lkp@intel.com> (raw)
Hi Mostafa,
First bad commit (maybe != root cause):
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 485f58484dd83e1f0ab5a620a88a0120bf605cdd
commit: 09de45521bacc85848722d3b15c846e584e51846 [1/1] ANDROID: KVM: arm64: Fix build issue without CONFIG_ARM64_LSE_ATOMICS
config: arm64-randconfig-r113-20240716 (https://download.01.org/0day-ci/archive/20240719/202407190840.0Hdo1DDB-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project a0c6b8aef853eedaa0980f07c0a502a5a8a9740e)
reproduce: (https://download.01.org/0day-ci/archive/20240719/202407190840.0Hdo1DDB-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/202407190840.0Hdo1DDB-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c:54:5: sparse: sparse: symbol 'kvm_arm_io_pgtable_init' was not declared. Should it be static?
--
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:198:25: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:198:25: sparse: expected unsigned long long [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:198:25: sparse: got restricted __le64 [usertype]
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:690:20: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *base @@ got void * @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:690:20: sparse: expected void [noderef] __iomem *base
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:690:20: sparse: got void *
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:741:5: sparse: sparse: symbol 'smmu_domain_config_s2' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:787:15: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:823:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:823:21: sparse: expected unsigned long long [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:823:21: sparse: got restricted __le64 [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:825:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:825:21: sparse: expected unsigned long long [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:825:21: sparse: got restricted __le64 [usertype]
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:840:9: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long volatile @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:840:9: sparse: expected unsigned long long volatile
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:840:9: sparse: got restricted __le64 [usertype]
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:773:5: sparse: sparse: symbol 'smmu_domain_config_s1' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:847:5: sparse: sparse: symbol 'smmu_domain_finalise' was not declared. Should it be static?
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:918:24: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:918:24: sparse: expected unsigned long long [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:918:24: sparse: got restricted __le64 [usertype]
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:924:9: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long volatile @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:924:9: sparse: expected unsigned long long volatile
drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:924:9: sparse: got restricted __le64 [usertype]
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:994:5: sparse: sparse: symbol 'smmu_alloc_domain' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:1011:6: sparse: sparse: symbol 'smmu_free_domain' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:1023:6: sparse: sparse: symbol 'smmu_dabt_device' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:1066:6: sparse: sparse: symbol 'smmu_dabt_handler' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:1078:5: sparse: sparse: symbol 'smmu_suspend' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c:1091:5: sparse: sparse: symbol 'smmu_resume' was not declared. Should it be static?
vim +/kvm_arm_io_pgtable_init +54 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 53
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 @54 int kvm_arm_io_pgtable_init(struct io_pgtable_cfg *cfg,
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 55 struct arm_lpae_io_pgtable *data)
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 56 {
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 57 int ret = -EINVAL;
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 58
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 59 if (cfg->fmt == ARM_64_LPAE_S2)
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 60 ret = arm_lpae_init_pgtable_s2(cfg, data);
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 61 else if (cfg->fmt == ARM_64_LPAE_S1)
27175bfef08dd78 drivers/iommu/arm/arm-smmu-v3/pkvm/io-pgtable-arm.c Mostafa Saleh 2023-08-12 62 ret = arm_lpae_init_pgtable_s1(cfg, data);
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 63
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 64 if (ret)
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 65 return ret;
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 66
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 67 data->iop.cfg = *cfg;
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 68 data->iop.fmt = cfg->fmt;
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 69
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 70 return 0;
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 71 }
cc07183cc836e2c arch/arm64/kvm/hyp/nvhe/iommu/io-pgtable-arm.c Jean-Philippe Brucker 2022-11-23 72
:::::: The code at line 54 was first introduced by commit
:::::: cc07183cc836e2c8e29a55ae6e8e2aa431d59170 BACKPORT: FROMLIST: KVM: arm64: smmu-v3: Support io-pgtable
:::::: TO: Jean-Philippe Brucker <jean-philippe@linaro.org>
:::::: CC: Mostafa Saleh <smostafa@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-19 0:50 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=202407190840.0Hdo1DDB-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.