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-desktop 0/1] drivers/gpu/drm/xe/xe_pxp_submit.c:46:45: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 14 Aug 2026 01:31:33 +0800 [thread overview]
Message-ID: <202608140159.uypsNqpe-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: 24c37396da197463e1ff2bc69bb789e34dacad53
commit: 4767008f9bff6399fe093c6ce4d7688e333ed671 [0/1] UPSTREAM: drm/xe/pxp: Allocate PXP execution resources
config: i386-randconfig-062-20260813 (https://download.01.org/0day-ci/archive/20260814/202608140159.uypsNqpe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608140159.uypsNqpe-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/202608140159.uypsNqpe-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/xe/xe_pxp_submit.c:46:45: sparse: sparse: Using plain integer as NULL pointer
vim +46 drivers/gpu/drm/xe/xe_pxp_submit.c
17
18 /*
19 * The VCS is used for kernel-owned GGTT submissions to issue key termination.
20 * Terminations are serialized, so we only need a single queue and a single
21 * batch.
22 */
23 static int allocate_vcs_execution_resources(struct xe_pxp *pxp)
24 {
25 struct xe_gt *gt = pxp->gt;
26 struct xe_device *xe = pxp->xe;
27 struct xe_tile *tile = gt_to_tile(gt);
28 struct xe_hw_engine *hwe;
29 struct xe_exec_queue *q;
30 struct xe_bo *bo;
31 int err;
32
33 hwe = xe_gt_hw_engine(gt, XE_ENGINE_CLASS_VIDEO_DECODE, 0, true);
34 if (!hwe)
35 return -ENODEV;
36
37 q = xe_exec_queue_create(xe, NULL, BIT(hwe->logical_instance), 1, hwe,
38 EXEC_QUEUE_FLAG_KERNEL | EXEC_QUEUE_FLAG_PERMANENT, 0);
39 if (IS_ERR(q))
40 return PTR_ERR(q);
41
42 /*
43 * Each termination is 16 DWORDS, so 4K is enough to contain a
44 * termination for each sessions.
45 */
> 46 bo = xe_bo_create_pin_map(xe, tile, 0, SZ_4K, ttm_bo_type_kernel,
47 XE_BO_FLAG_SYSTEM | XE_BO_FLAG_PINNED | XE_BO_FLAG_GGTT);
48 if (IS_ERR(bo)) {
49 err = PTR_ERR(bo);
50 goto out_queue;
51 }
52
53 pxp->vcs_exec.q = q;
54 pxp->vcs_exec.bo = bo;
55
56 return 0;
57
58 out_queue:
59 xe_exec_queue_put(q);
60 return err;
61 }
62
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-13 17:32 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=202608140159.uypsNqpe-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.