From: kernel test robot <lkp@intel.com>
To: Haren Myneni <haren@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Subject: arch/powerpc/platforms/pseries/vas.c:186:13: sparse: sparse: symbol 'pseries_vas_fault_thread_fn' was not declared. Should it be static?
Date: Tue, 27 Jul 2021 19:00:04 +0800 [thread overview]
Message-ID: <202107271835.eFiwodUS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ff1176468d368232b684f75e82563369208bc371
commit: 6d0aaf5e0de00491de136f387ebed55604cedebe powerpc/pseries/vas: Setup IRQ and fault handling
date: 5 weeks ago
config: powerpc-randconfig-s031-20210727 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 10.3.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.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0aaf5e0de00491de136f387ebed55604cedebe
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 6d0aaf5e0de00491de136f387ebed55604cedebe
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=powerpc SHELL=/bin/bash arch/powerpc/platforms/pseries/ drivers/crypto/nx/
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/powerpc/platforms/pseries/vas.c:186:13: sparse: sparse: symbol 'pseries_vas_fault_thread_fn' was not declared. Should it be static?
vim +/pseries_vas_fault_thread_fn +186 arch/powerpc/platforms/pseries/vas.c
177
178 /*
179 * Handle the fault interrupt.
180 * When the fault interrupt is received for each window, query the
181 * hypervisor to get the fault CRB on the specific fault. Then
182 * process the CRB by updating CSB or send signal if the user space
183 * CSB is invalid.
184 * Note: The hypervisor forwards an interrupt for each fault request.
185 * So one fault CRB to process for each H_GET_NX_FAULT hcall.
> 186 */
187 irqreturn_t pseries_vas_fault_thread_fn(int irq, void *data)
188 {
189 struct pseries_vas_window *txwin = data;
190 struct coprocessor_request_block crb;
191 struct vas_user_win_ref *tsk_ref;
192 int rc;
193
194 rc = h_get_nx_fault(txwin->vas_win.winid, (u64)virt_to_phys(&crb));
195 if (!rc) {
196 tsk_ref = &txwin->vas_win.task_ref;
197 vas_dump_crb(&crb);
198 vas_update_csb(&crb, tsk_ref);
199 }
200
201 return IRQ_HANDLED;
202 }
203
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29364 bytes --]
reply other threads:[~2021-07-27 11:00 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=202107271835.eFiwodUS-lkp@intel.com \
--to=lkp@intel.com \
--cc=haren@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 NNTP newsgroup(s).