From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android13-5.10 17571/30000] arch/arm64/kvm/hyp/nvhe/psci-relay.c:249:6: warning: no previous prototype for 'psci_mem_protect_inc'
Date: Mon, 15 Jan 2024 16:13:56 +0800 [thread overview]
Message-ID: <202401151643.mLcl4xVa-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android13-5.10
head: 57bec5e659b43d5c29cd8678f5888f3bf2594bcf
commit: ba73e0b827383ff4ede2036f5bae8424896139f3 [17571/30000] ANDROID: KVM: arm64: Use PSCI MEM_PROTECT to zap guest pages on reset
config: arm64-randconfig-r016-20230905 (https://download.01.org/0day-ci/archive/20240115/202401151643.mLcl4xVa-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240115/202401151643.mLcl4xVa-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/202401151643.mLcl4xVa-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/arm64/kvm/hyp/nvhe/psci-relay.c:204:28: warning: no previous prototype for 'kvm_host_psci_cpu_entry' [-Wmissing-prototypes]
204 | asmlinkage void __noreturn kvm_host_psci_cpu_entry(bool is_cpu_on)
| ^~~~~~~~~~~~~~~~~~~~~~~
>> arch/arm64/kvm/hyp/nvhe/psci-relay.c:249:6: warning: no previous prototype for 'psci_mem_protect_inc' [-Wmissing-prototypes]
249 | void psci_mem_protect_inc(void)
| ^~~~~~~~~~~~~~~~~~~~
>> arch/arm64/kvm/hyp/nvhe/psci-relay.c:256:6: warning: no previous prototype for 'psci_mem_protect_dec' [-Wmissing-prototypes]
256 | void psci_mem_protect_dec(void)
| ^~~~~~~~~~~~~~~~~~~~
vim +/psci_mem_protect_inc +249 arch/arm64/kvm/hyp/nvhe/psci-relay.c
248
> 249 void psci_mem_protect_inc(void)
250 {
251 hyp_spin_lock(&mem_protect_lock);
252 psci_mem_protect(1);
253 hyp_spin_unlock(&mem_protect_lock);
254 }
255
> 256 void psci_mem_protect_dec(void)
257 {
258 hyp_spin_lock(&mem_protect_lock);
259 psci_mem_protect(-1);
260 hyp_spin_unlock(&mem_protect_lock);
261 }
262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-15 8:17 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=202401151643.mLcl4xVa-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.