From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/x86/kernel/cpu/debugfs.c:11:33: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Fri, 1 Dec 2023 04:21:08 +0800 [thread overview]
Message-ID: <202312010444.uoDYtflb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3b47bc037bd44f142ac09848e8d3ecccc726be99
commit: 48525fd1ea1cfa059a580e77b10ea8790914efa2 x86/cpu: Provide debug interface
date: 7 weeks ago
config: i386-randconfig-061-20231014 (https://download.01.org/0day-ci/archive/20231201/202312010444.uoDYtflb-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231201/202312010444.uoDYtflb-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/202312010444.uoDYtflb-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/cpu/debugfs.c:11:33: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct cpuinfo_x86 * @@
arch/x86/kernel/cpu/debugfs.c:11:33: sparse: expected void const [noderef] __percpu *__vpp_verify
arch/x86/kernel/cpu/debugfs.c:11:33: sparse: got struct cpuinfo_x86 *
vim +11 arch/x86/kernel/cpu/debugfs.c
7
8 static int cpu_debug_show(struct seq_file *m, void *p)
9 {
10 unsigned long cpu = (unsigned long)m->private;
> 11 struct cpuinfo_x86 *c = per_cpu_ptr(&cpu_info, cpu);
12
13 seq_printf(m, "online: %d\n", cpu_online(cpu));
14 if (!c->initialized)
15 return 0;
16
17 seq_printf(m, "initial_apicid: %x\n", c->topo.initial_apicid);
18 seq_printf(m, "apicid: %x\n", c->topo.apicid);
19 seq_printf(m, "pkg_id: %u\n", c->topo.pkg_id);
20 seq_printf(m, "die_id: %u\n", c->topo.die_id);
21 seq_printf(m, "cu_id: %u\n", c->topo.cu_id);
22 seq_printf(m, "core_id: %u\n", c->topo.core_id);
23 seq_printf(m, "logical_pkg_id: %u\n", c->topo.logical_pkg_id);
24 seq_printf(m, "logical_die_id: %u\n", c->topo.logical_die_id);
25 seq_printf(m, "llc_id: %u\n", c->topo.llc_id);
26 seq_printf(m, "l2c_id: %u\n", c->topo.l2c_id);
27 seq_printf(m, "max_cores: %u\n", c->x86_max_cores);
28 seq_printf(m, "max_die_per_pkg: %u\n", __max_die_per_package);
29 seq_printf(m, "smp_num_siblings: %u\n", smp_num_siblings);
30 return 0;
31 }
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-30 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 20:21 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 8:05 arch/x86/kernel/cpu/debugfs.c:11:33: sparse: sparse: incorrect type in initializer (different address spaces) kernel test robot
2024-03-01 23:38 kernel test robot
2024-03-01 23:49 ` Thomas Gleixner
2024-03-02 12:57 ` Yujie Liu
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=202312010444.uoDYtflb-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
/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