mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Marc Zyngier <maz@kernel.org>
Subject: arch/arm64/kvm/arm.c:64:1: sparse: sparse: symbol '__pcpu_scope_kvm_arm_hyp_stack_base' was not declared. Should it be static?
Date: Tue, 16 Dec 2025 14:29:36 +0800	[thread overview]
Message-ID: <202512161450.H8u3Nf3Z-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   8f0b4cce4481fb22653697cced8d0d04027cb1e8
commit: 38f9e4b905a00047a96fbdc6cefe9ceb4dae34c3 arm64: kvm: Introduce nvhe stack size constants
date:   11 months ago
config: arm64-randconfig-r112-20251216 (https://download.01.org/0day-ci/archive/20251216/202512161450.H8u3Nf3Z-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251216/202512161450.H8u3Nf3Z-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/202512161450.H8u3Nf3Z-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/arm.c:64:1: sparse: sparse: symbol '__pcpu_scope_kvm_arm_hyp_stack_base' was not declared. Should it be static?
   arch/arm64/kvm/arm.c:241:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   arch/arm64/kvm/arm.c:241:16: sparse:    struct kvm_mpidr_data [noderef] __rcu *
   arch/arm64/kvm/arm.c:241:16: sparse:    struct kvm_mpidr_data *
   arch/arm64/kvm/arm.c:244:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
   arch/arm64/kvm/arm.c:244:17: sparse:    struct kvm_mpidr_data [noderef] __rcu *
   arch/arm64/kvm/arm.c:244:17: sparse:    struct kvm_mpidr_data *
   arch/arm64/kvm/arm.c:743:13: sparse: sparse: incompatible types in comparison expression (different address spaces):
   arch/arm64/kvm/arm.c:743:13: sparse:    struct kvm_mpidr_data [noderef] __rcu *
   arch/arm64/kvm/arm.c:743:13: sparse:    struct kvm_mpidr_data *
   arch/arm64/kvm/arm.c:781:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   arch/arm64/kvm/arm.c:781:9: sparse:    struct kvm_mpidr_data [noderef] __rcu *
   arch/arm64/kvm/arm.c:781:9: sparse:    struct kvm_mpidr_data *
   arch/arm64/kvm/arm.c:2681:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   arch/arm64/kvm/arm.c:2681:16: sparse:    struct kvm_mpidr_data [noderef] __rcu *
   arch/arm64/kvm/arm.c:2681:16: sparse:    struct kvm_mpidr_data *

vim +/__pcpu_scope_kvm_arm_hyp_stack_base +64 arch/arm64/kvm/arm.c

    63	
  > 64	DEFINE_PER_CPU(unsigned long, kvm_arm_hyp_stack_base);
    65	DECLARE_KVM_NVHE_PER_CPU(struct kvm_nvhe_init_params, kvm_init_params);
    66	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-12-16  6:30 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=202512161450.H8u3Nf3Z-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®