From: kernel test robot <lkp@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-ia64@vger.kernel.org
Subject: [aegl:rdt-aet-v5 28/29] arch/x86/kernel/cpu/resctrl/intel_aet.c:288:63: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Wed, 21 May 2025 15:55:40 +0800 [thread overview]
Message-ID: <202505211506.gIuGNQZ7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git rdt-aet-v5
head: a0273c92f4de70daf85926f88e122a66de5bf943
commit: 113e20da9990a521c6106188f9c662fc9f745bb3 [28/29] x86/resctrl: Add info/PERF_PKG_MON/status file
config: x86_64-randconfig-121-20250521 (https://download.01.org/0day-ci/archive/20250521/202505211506.gIuGNQZ7-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250521/202505211506.gIuGNQZ7-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/202505211506.gIuGNQZ7-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/cpu/resctrl/intel_aet.c:288:63: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void *[noderef] __iomem info @@ got void [noderef] __iomem * @@
arch/x86/kernel/cpu/resctrl/intel_aet.c:288:63: sparse: expected void *[noderef] __iomem info
arch/x86/kernel/cpu/resctrl/intel_aet.c:288:63: sparse: got void [noderef] __iomem *
>> arch/x86/kernel/cpu/resctrl/intel_aet.c:292:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *addr @@ got void * @@
arch/x86/kernel/cpu/resctrl/intel_aet.c:292:31: sparse: expected void const volatile [noderef] __iomem *addr
arch/x86/kernel/cpu/resctrl/intel_aet.c:292:31: sparse: got void *
arch/x86/kernel/cpu/resctrl/intel_aet.c:294:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *addr @@ got void * @@
arch/x86/kernel/cpu/resctrl/intel_aet.c:294:31: sparse: expected void const volatile [noderef] __iomem *addr
arch/x86/kernel/cpu/resctrl/intel_aet.c:294:31: sparse: got void *
arch/x86/kernel/cpu/resctrl/intel_aet.c:296:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *addr @@ got void * @@
arch/x86/kernel/cpu/resctrl/intel_aet.c:296:31: sparse: expected void const volatile [noderef] __iomem *addr
arch/x86/kernel/cpu/resctrl/intel_aet.c:296:31: sparse: got void *
arch/x86/kernel/cpu/resctrl/intel_aet.c:292:26: sparse: sparse: dereference of noderef expression
arch/x86/kernel/cpu/resctrl/intel_aet.c:292:26: sparse: sparse: dereference of noderef expression
arch/x86/kernel/cpu/resctrl/intel_aet.c:294:26: sparse: sparse: dereference of noderef expression
arch/x86/kernel/cpu/resctrl/intel_aet.c:294:26: sparse: sparse: dereference of noderef expression
arch/x86/kernel/cpu/resctrl/intel_aet.c:296:26: sparse: sparse: dereference of noderef expression
arch/x86/kernel/cpu/resctrl/intel_aet.c:296:26: sparse: sparse: dereference of noderef expression
vim +288 arch/x86/kernel/cpu/resctrl/intel_aet.c
285
286 static void show_debug(struct seq_file *s, struct event_group *e, int pkg, int instance)
287 {
> 288 void *info __iomem = e->pkginfo[pkg]->addrs[instance] + e->mmio_size;
289
290 /* Information registers are the last three qwords in MMIO space */
291 seq_printf(s, "%s %d:%d agg_data_loss_count = %llu\n", e->name, pkg, instance,
> 292 readq(info - 24));
293 seq_printf(s, "%s %d:%d agg_data_loss_timestamp = %llu\n", e->name, pkg, instance,
294 readq(info - 16));
295 seq_printf(s, "%s %d:%d last_update_timestamp = %llu\n", e->name, pkg, instance,
296 readq(info - 8));
297 }
298
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-21 7:56 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=202505211506.gIuGNQZ7-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tony.luck@intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).