From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 1/1] arch/arm64/kvm/hyp/nvhe/power/scmi.c:215:36: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Fri, 7 Mar 2025 12:53:47 +0800 [thread overview]
Message-ID: <202503071256.PHb434VH-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 7d22ae2248e26f0c940277ad47f974ba897a7fa8
commit: 220be807706d350ba6a1f17f0a3586269d844eda [1/1] BACKPORT: FROMLIST: KVM: arm64: pkvm: Support SCMI power domain
config: arm64-randconfig-r122-20250307 (https://download.01.org/0day-ci/archive/20250307/202503071256.PHb434VH-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250307/202503071256.PHb434VH-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/202503071256.PHb434VH-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/hyp/nvhe/power/scmi.c:215:36: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *static [assigned] [toplevel] shmem @@ got void * @@
arch/arm64/kvm/hyp/nvhe/power/scmi.c:215:36: sparse: expected void [noderef] __iomem *static [assigned] [toplevel] shmem
arch/arm64/kvm/hyp/nvhe/power/scmi.c:215:36: sparse: got void *
vim +215 arch/arm64/kvm/hyp/nvhe/power/scmi.c
191
192 int pkvm_init_scmi_pd(struct kvm_power_domain *pd,
193 const struct kvm_power_domain_ops *ops)
194 {
195 int ret;
196
197 if (!IS_ALIGNED(pd->arm_scmi.shmem_base, PAGE_SIZE) ||
198 pd->arm_scmi.shmem_size < PAGE_SIZE) {
199 return -EINVAL;
200 }
201
202 if (!scmi_channel.shmem) {
203 unsigned long shmem;
204
205 /* FIXME: Do we need to mark those pages shared in the host s2? */
206 ret = __pkvm_create_private_mapping(pd->arm_scmi.shmem_base,
207 pd->arm_scmi.shmem_size,
208 PAGE_HYP_DEVICE,
209 &shmem);
210 if (ret)
211 return ret;
212
213 scmi_channel.smc_id = pd->arm_scmi.smc_id;
214 scmi_channel.shmem_pfn = hyp_phys_to_pfn(pd->arm_scmi.shmem_base);
> 215 scmi_channel.shmem = (void *)shmem;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-07 4:54 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=202503071256.PHb434VH-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.