All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 1/1] arch/arm64/kvm/handle_exit.c:495:48: sparse: sparse: cast to restricted gfp_t
Date: Fri, 27 Feb 2026 21:48:02 +0800	[thread overview]
Message-ID: <202602272110.qUW9bDP0-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android17-6.18
head:   71f2074b8c1e4e009b1e126ca1a2a9ce14201030
commit: d0c5a9934e73da6103c39838c3d03b849731962d [1/1] ANDROID: KVM: arm64: Generalize kvm_hyp_req ser/des to smccc
config: arm64-randconfig-r132-20260227 (https://download.01.org/0day-ci/archive/20260227/202602272110.qUW9bDP0-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260227/202602272110.qUW9bDP0-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/202602272110.qUW9bDP0-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/handle_exit.c:495:48: sparse: sparse: cast to restricted gfp_t
--
>> arch/arm64/kvm/iommu.c:178:16: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:187:16: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:203:16: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:224:26: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:252:28: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:310:16: sparse: sparse: cast from restricted gfp_t
   arch/arm64/kvm/iommu.c:358:26: sparse: sparse: cast from restricted gfp_t

vim +495 arch/arm64/kvm/handle_exit.c

   486	
   487	int handle_hyp_req(struct kvm_vcpu *vcpu, struct kvm_hyp_req *req, void *arg)
   488	{
   489		switch (req->type) {
   490		case KVM_HYP_REQ_TYPE_HYP_ALLOC:
   491			return __pkvm_topup_hyp_alloc(req->mem.nr_pages);
   492	
   493		case KVM_HYP_REQ_TYPE_MEM_IOMMU:
   494			return __pkvm_topup_hyp_iommu(1, req->mem.nr_pages << PAGE_SHIFT,
 > 495						      (gfp_t)(uintptr_t)arg);
   496	
   497		case KVM_HYP_REQ_TYPE_MEM:
   498			return handle_hyp_req_mem(vcpu, req);
   499	
   500		case KVM_HYP_REQ_TYPE_MAP:
   501			if (!vcpu)
   502				return -EINVAL;
   503			return pkvm_mem_abort_range(vcpu, req->map.guest_ipa, req->map.size);
   504	
   505		case KVM_HYP_REQ_TYPE_SPLIT:
   506			if (!vcpu)
   507				return -EINVAL;
   508			return __pkvm_pgtable_stage2_split(vcpu, req->split.guest_ipa, req->split.size);
   509	
   510		case KVM_HYP_LAST_REQ:
   511			return 0;
   512		}
   513	
   514		pr_warn("Unknown kvm_hyp_req type: %d\n", req->type);
   515		return -EINVAL;
   516	}
   517	

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

             reply	other threads:[~2026-02-27 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 13:48 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-05  9:51 [android-common:android17-6.18 1/1] arch/arm64/kvm/handle_exit.c:495:48: sparse: sparse: cast to restricted gfp_t kernel test robot
2026-11-06  6:27 kernel test robot

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=202602272110.qUW9bDP0-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.