From: kernel test robot <lkp@intel.com>
To: Fares Mehanna <faresx@amazon.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 7/7] arm64: KVM: Allocate vCPU fp-regs dynamically on VHE and KERNEL_SECRETMEM enabled systems
Date: Sun, 15 Sep 2024 08:44:32 +0800 [thread overview]
Message-ID: <202409150822.gguVxnNM-lkp@intel.com> (raw)
In-Reply-To: <20240911143421.85612-8-faresx@amazon.de>
Hi Fares,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on linus/master v6.11-rc7]
[cannot apply to kvmarm/next akpm-mm/mm-everything next-20240913]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Fares-Mehanna/mseal-expose-interface-to-seal-unseal-user-memory-ranges/20240911-223945
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
patch link: https://lore.kernel.org/r/20240911143421.85612-8-faresx%40amazon.de
patch subject: [RFC PATCH 7/7] arm64: KVM: Allocate vCPU fp-regs dynamically on VHE and KERNEL_SECRETMEM enabled systems
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20240915/202409150822.gguVxnNM-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project bf684034844c660b778f0eba103582f582b710c9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240915/202409150822.gguVxnNM-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/202409150822.gguVxnNM-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/arm64/kvm/va_layout.c:7:
In file included from include/linux/kvm_host.h:16:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:500:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
500 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
501 | item];
| ~~~~
include/linux/vmstat.h:507:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
507 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
508 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:514:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
514 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
include/linux/vmstat.h:519:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
519 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
520 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:528:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
528 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
529 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
arch/arm64/kvm/va_layout.c:212:13: warning: no previous prototype for function 'kvm_update_ctxt_gp_regs' [-Wmissing-prototypes]
212 | void __init kvm_update_ctxt_gp_regs(struct alt_instr *alt,
| ^
arch/arm64/kvm/va_layout.c:212:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
212 | void __init kvm_update_ctxt_gp_regs(struct alt_instr *alt,
| ^
| static
>> arch/arm64/kvm/va_layout.c:219:13: warning: no previous prototype for function 'kvm_update_ctxt_fp_regs' [-Wmissing-prototypes]
219 | void __init kvm_update_ctxt_fp_regs(struct alt_instr *alt,
| ^
arch/arm64/kvm/va_layout.c:219:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
219 | void __init kvm_update_ctxt_fp_regs(struct alt_instr *alt,
| ^
| static
7 warnings generated.
vim +/kvm_update_ctxt_fp_regs +219 arch/arm64/kvm/va_layout.c
218
> 219 void __init kvm_update_ctxt_fp_regs(struct alt_instr *alt,
220 __le32 *origptr, __le32 *updptr, int nr_inst)
221 {
222 u32 offset = offsetof(struct kvm_cpu_context, fp_regs);
223 kvm_update_ctxt_regs(alt, origptr, updptr, nr_inst, offset);
224 }
225
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-09-15 0:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240911143421.85612-8-faresx@amazon.de>]
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=202409150822.gguVxnNM-lkp@intel.com \
--to=lkp@intel.com \
--cc=faresx@amazon.de \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox