From: kernel test robot <lkp@intel.com>
To: Anup Patel <anup.patel@wdc.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [avpatel:riscv_kvm_aia_v1 3/28] arch/riscv/kernel/smp.c:176:50: sparse: sparse: incorrect type in argument 4 (different address spaces)
Date: Sat, 27 Nov 2021 07:53:09 +0800 [thread overview]
Message-ID: <202111270742.xpkU8cDl-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_kvm_aia_v1
head: d3147cebc4aa570424c3bc2ac18831bc3d3bd2d6
commit: 9779a6720c22960d01ea1622f1f433e7dcb473f8 [3/28] RISC-V: Treat IPIs as normal Linux IRQs
config: riscv-randconfig-s032-20211126 (https://download.01.org/0day-ci/archive/20211127/202111270742.xpkU8cDl-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/avpatel/linux/commit/9779a6720c22960d01ea1622f1f433e7dcb473f8
git remote add avpatel https://github.com/avpatel/linux.git
git fetch --no-tags avpatel riscv_kvm_aia_v1
git checkout 9779a6720c22960d01ea1622f1f433e7dcb473f8
# save the config file to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/riscv/kernel/smp.c:176:50: sparse: sparse: incorrect type in argument 4 (different address spaces) @@ expected void [noderef] __percpu *percpu_dev_id @@ got int * @@
arch/riscv/kernel/smp.c:176:50: sparse: expected void [noderef] __percpu *percpu_dev_id
arch/riscv/kernel/smp.c:176:50: sparse: got int *
vim +176 arch/riscv/kernel/smp.c
161
162 void riscv_ipi_set_virq_range(int virq, int nr)
163 {
164 int i, err;
165
166 if (WARN_ON(ipi_virq_base))
167 return;
168
169 WARN_ON(nr < IPI_MAX);
170 nr_ipi = min(nr, IPI_MAX);
171 ipi_virq_base = virq;
172
173 /* Request IPIs */
174 for (i = 0; i < nr_ipi; i++) {
175 err = request_percpu_irq(ipi_virq_base + i, handle_IPI,
> 176 "IPI", &ipi_virq_base);
177 WARN_ON(err);
178
179 ipi_desc[i] = irq_to_desc(ipi_virq_base + i);
180 irq_set_status_flags(ipi_virq_base + i, IRQ_HIDDEN);
181 }
182
183 /* Enabled IPIs for boot CPU immediately */
184 riscv_ipi_enable();
185 }
186 EXPORT_SYMBOL_GPL(riscv_ipi_set_virq_range);
187
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-11-26 23:55 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=202111270742.xpkU8cDl-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup.patel@wdc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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®