From: kernel test robot <lkp@intel.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [intel-tdx:kvm-upstream-workaround 312/338] arch/x86/kvm/mmu/mmu.c:713:5: warning: no previous prototype for function 'kvm_mmu_topup_memory_cache_for_split'
Date: Tue, 25 Apr 2023 06:45:34 +0800 [thread overview]
Message-ID: <202304250651.Pftd0rsh-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 5217810067c6f32309d1473fc94649608330885c
commit: a51188903783ebbcbc6cd13b599fc53b3d5e6695 [312/338] [REVERTME] KVM: TDX, x86/tdp_mmu: Protect Secure-EPT page
config: x86_64-randconfig-a014 (https://download.01.org/0day-ci/archive/20230425/202304250651.Pftd0rsh-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel/tdx/commit/a51188903783ebbcbc6cd13b599fc53b3d5e6695
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout a51188903783ebbcbc6cd13b599fc53b3d5e6695
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kvm/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304250651.Pftd0rsh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kvm/mmu/mmu.c:713:5: warning: no previous prototype for function 'kvm_mmu_topup_memory_cache_for_split' [-Wmissing-prototypes]
int kvm_mmu_topup_memory_cache_for_split(struct kvm *kvm)
^
arch/x86/kvm/mmu/mmu.c:713:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int kvm_mmu_topup_memory_cache_for_split(struct kvm *kvm)
^
static
1 warning generated.
vim +/kvm_mmu_topup_memory_cache_for_split +713 arch/x86/kvm/mmu/mmu.c
712
> 713 int kvm_mmu_topup_memory_cache_for_split(struct kvm *kvm)
714 {
715 int r = 0;
716 #ifdef CONFIG_INTEL_TDX_HOST_DEBUG_MEMORY_CORRUPT
717 struct kvm_mmu_memory_cache *mc;
718 int start, end, i;
719
720 mutex_lock(&kvm->arch.private_spt_for_split_lock);
721 mc = &kvm->arch.private_spt_for_split_cache;
722 start = kvm_mmu_memory_cache_nr_free_objects(mc);
723 r = kvm_mmu_topup_memory_cache(mc, KVM_MAX_HUGEPAGE_LEVEL *
724 kvm->created_vcpus);
725 end = kvm_mmu_memory_cache_nr_free_objects(mc);
726 for (i = start; i < end; i++)
727 kvm_mmu_split_direct_map(virt_to_page(mc->objects[i]));
728 mutex_unlock(&kvm->arch.private_spt_for_split_lock);
729 #endif
730 return r;
731 }
732
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-04-24 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 22:45 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-30 7:58 [intel-tdx:kvm-upstream-workaround 312/338] arch/x86/kvm/mmu/mmu.c:713:5: warning: no previous prototype for function 'kvm_mmu_topup_memory_cache_for_split' kernel test robot
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=202304250651.Pftd0rsh-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--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 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.