From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 5609/8449] arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 19 Sep 2026 17:42:42 +0800 [thread overview]
Message-ID: <202609191703.VLP7KJSb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3f2425f5b5bbbdd991ca9cdfd5502e68d8895998
commit: 892fc33977cf8b2cf98065e5ae532e4ddbbe09cc [5609/8449] Merge branch kvm-arm64/hyp-type-checking-7.4 into kvmarm-master/next
config: arm64-randconfig-r1307-20260918 (https://download.01.org/0day-ci/archive/20260919/202609191703.VLP7KJSb-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 7252edd9aa82ef1c570ff6694ef7f4763a8a5d2f)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260919/202609191703.VLP7KJSb-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/202609191703.VLP7KJSb-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: sparse: symbol '__do___vgic_v5_make_resident' redeclared with different type (incompatible argument 1 (different address spaces)):
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: void static [toplevel] __do___vgic_v5_make_resident( ... )
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: note: previously declared as:
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: void static [toplevel] [usertype] __do___vgic_v5_make_resident( ... )
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: sparse: symbol '__do___vgic_v5_make_non_resident' redeclared with different type (incompatible argument 1 (different address spaces)):
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: void static [toplevel] __do___vgic_v5_make_non_resident( ... )
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: note: previously declared as:
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: void static [toplevel] [usertype] __do___vgic_v5_make_non_resident( ... )
>> arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct vgic_v5_cpu_if *cpu_if @@ got struct vgic_v5_cpu_if [noderef] __kern * @@
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: expected struct vgic_v5_cpu_if *cpu_if
arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: got struct vgic_v5_cpu_if [noderef] __kern *
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct vgic_v5_cpu_if *cpu_if @@ got struct vgic_v5_cpu_if [noderef] __kern * @@
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: expected struct vgic_v5_cpu_if *cpu_if
arch/arm64/kvm/hyp/nvhe/hyp-main.c:858:1: sparse: got struct vgic_v5_cpu_if [noderef] __kern *
vim +849 arch/arm64/kvm/hyp/nvhe/hyp-main.c
848
> 849 DEFINE_KVM_HOST_HCALL(void, __vgic_v5_make_resident,
850 struct vgic_v5_cpu_if __kern *, cpu_if)
851 {
852 if (unlikely(is_protected_kvm_enabled()))
853 return;
854
855 __vgic_v5_make_resident(kern_hyp_va_host(cpu_if));
856 }
857
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-19 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 9:42 kernel test robot [this message]
2026-09-19 12:16 ` [linux-next:master 5609/8449] arch/arm64/kvm/hyp/nvhe/hyp-main.c:849:1: sparse: sparse: incorrect type in argument 1 (different address spaces) Marc Zyngier
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=202609191703.VLP7KJSb-lkp@intel.com \
--to=lkp@intel.com \
--cc=maz@kernel.org \
--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.