From: kernel test robot <lkp@intel.com>
To: Chao Gao <chao.gao@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>,
Zeng Guang <guang.zeng@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [intel-tdx:kvm-upstream-workaround 99/361] arch/x86/kvm/vmx/vmx.c:4410:5: warning: no previous prototype for 'vmx_get_pid_table_order'
Date: Fri, 6 May 2022 05:26:48 +0800 [thread overview]
Message-ID: <202205060503.iU8bElBs-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 3b5b338cdf10dca7a2435d1f86b2dd9f1a3ad833
commit: 833404c859e4357ba656b2d19d5a405ba7bf4ec4 [99/361] KVM: VMX: enable IPI virtualization
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220506/202205060503.iU8bElBs-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# 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 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>
All warnings (new ones prefixed by >>):
>> arch/x86/kvm/vmx/vmx.c:4410:5: warning: no previous prototype for 'vmx_get_pid_table_order' [-Wmissing-prototypes]
4410 | int vmx_get_pid_table_order(struct kvm *kvm)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/vmx_get_pid_table_order +4410 arch/x86/kvm/vmx/vmx.c
4409
> 4410 int vmx_get_pid_table_order(struct kvm *kvm)
4411 {
4412 return get_order(kvm->arch.max_vcpu_ids * sizeof(*to_kvm_vmx(kvm)->pid_table));
4413 }
4414
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-05 21:27 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=202205060503.iU8bElBs-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao.gao@intel.com \
--cc=guang.zeng@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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
all inboxes | Powered by JetHome®