From: kernel test robot <lkp@intel.com>
To: Kajol Jain <kjain@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: arch/powerpc/perf/vpa-dtl.c:254:30: sparse: sparse: incorrect type in assignment (different base types)
Date: Mon, 15 Dec 2025 15:05:27 +0800 [thread overview]
Message-ID: <202512151425.cwUtLbPF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
commit: 4708fba19adee9ba14ef28af6face4ab043d9cd6 powerpc/vpa_dtl: Add interface to expose vpa dtl counters via perf
date: 3 months ago
config: powerpc64-randconfig-r133-20251215 (https://download.01.org/0day-ci/archive/20251215/202512151425.cwUtLbPF-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251215/202512151425.cwUtLbPF-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/202512151425.cwUtLbPF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/powerpc/perf/vpa-dtl.c:254:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __be32 [usertype] @@
arch/powerpc/perf/vpa-dtl.c:254:30: sparse: expected unsigned int [usertype]
arch/powerpc/perf/vpa-dtl.c:254:30: sparse: got restricted __be32 [usertype]
vim +254 arch/powerpc/perf/vpa-dtl.c
241
242 static int vpa_dtl_event_add(struct perf_event *event, int flags)
243 {
244 int ret, hwcpu;
245 unsigned long addr;
246 struct vpa_dtl *dtl = &per_cpu(vpa_dtl_cpu, event->cpu);
247
248 /*
249 * Register our dtl buffer with the hypervisor. The
250 * HV expects the buffer size to be passed in the second
251 * word of the buffer. Refer section '14.11.3.2. H_REGISTER_VPA'
252 * from PAPR for more information.
253 */
> 254 ((u32 *)dtl->buf)[1] = cpu_to_be32(DISPATCH_LOG_BYTES);
255 dtl->last_idx = 0;
256
257 hwcpu = get_hard_smp_processor_id(event->cpu);
258 addr = __pa(dtl->buf);
259
260 ret = register_dtl(hwcpu, addr);
261 if (ret) {
262 pr_warn("DTL registration for cpu %d (hw %d) failed with %d\n",
263 event->cpu, hwcpu, ret);
264 return ret;
265 }
266
267 /* set our initial buffer indices */
268 lppaca_of(event->cpu).dtl_idx = 0;
269
270 /*
271 * Ensure that our updates to the lppaca fields have
272 * occurred before we actually enable the logging
273 */
274 smp_wmb();
275
276 /* enable event logging */
277 lppaca_of(event->cpu).dtl_enable_mask = event->attr.config;
278
279 vpa_dtl_start_hrtimer(event);
280
281 return 0;
282 }
283
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-15 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 7:05 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-17 16:01 arch/powerpc/perf/vpa-dtl.c:254:30: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2026-05-13 20:46 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=202512151425.cwUtLbPF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.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.