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,
Peter Zijlstra <peterz@infradead.org>
Subject: arch/x86/kernel/callthunks.c:303:20: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Sun, 30 Jul 2023 04:41:28 +0800 [thread overview]
Message-ID: <202307300433.nmumrsXO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 12214540ad87ce824a8a791a3f063e6121ec5b66
commit: f5c1bb2afe93396d41c5cbdcb909b08a75b8dde4 x86/calldepth: Add ret/call counting for debug
date: 10 months ago
config: x86_64-randconfig-x062-20230729 (https://download.01.org/0day-ci/archive/20230730/202307300433.nmumrsXO-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230730/202307300433.nmumrsXO-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/202307300433.nmumrsXO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/callthunks.c:303:20: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got unsigned long long * @@
arch/x86/kernel/callthunks.c:303:20: sparse: expected void const [noderef] __percpu *__vpp_verify
arch/x86/kernel/callthunks.c:303:20: sparse: got unsigned long long *
arch/x86/kernel/callthunks.c:306:20: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got unsigned long long * @@
arch/x86/kernel/callthunks.c:306:20: sparse: expected void const [noderef] __percpu *__vpp_verify
arch/x86/kernel/callthunks.c:306:20: sparse: got unsigned long long *
vim +303 arch/x86/kernel/callthunks.c
296
297 #if defined(CONFIG_CALL_THUNKS_DEBUG) && defined(CONFIG_DEBUG_FS)
298 static int callthunks_debug_show(struct seq_file *m, void *p)
299 {
300 unsigned long cpu = (unsigned long)m->private;
301
302 seq_printf(m, "C: %16llu R: %16llu S: %16llu X: %16llu\n,",
> 303 per_cpu(__x86_call_count, cpu),
304 per_cpu(__x86_ret_count, cpu),
305 per_cpu(__x86_stuffs_count, cpu),
306 per_cpu(__x86_ctxsw_count, cpu));
307 return 0;
308 }
309
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-07-29 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 20:41 kernel test robot [this message]
2023-09-28 20:28 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=202307300433.nmumrsXO-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®