* [intel-tdx:kvm-upstream-workaround 99/361] arch/x86/kvm/vmx/vmx.c:4410:5: sparse: sparse: symbol 'vmx_get_pid_table_order' was not declared. Should it be static?
@ 2022-05-07 10:58 kernel test robot
0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2022-05-07 10:58 UTC (permalink / raw)
To: Chao Gao
Cc: kbuild-all, linux-kernel, Isaku Yamahata, Zeng Guang,
Paolo Bonzini
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 3b5b338cdf10dca7a2435d1f86b2dd9f1a3ad833
commit: 833404c859e4357ba656b2d19d5a405ba7bf4ec4 [99/361] KVM: VMX: enable IPI virtualization
config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20220507/202205071817.k6ejQDOR-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/intel/tdx/commit/833404c859e4357ba656b2d19d5a405ba7bf4ec4
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout 833404c859e4357ba656b2d19d5a405ba7bf4ec4
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kvm/
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/x86/kvm/vmx/vmx.c:4410:5: sparse: sparse: symbol 'vmx_get_pid_table_order' was not declared. Should it be static?
Please review and possibly fold the followup patch.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-05-07 10:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-05-07 10:58 [intel-tdx:kvm-upstream-workaround 99/361] arch/x86/kvm/vmx/vmx.c:4410:5: sparse: sparse: symbol 'vmx_get_pid_table_order' was not declared. Should it be static? kernel test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox