All of lore.kernel.org
 help / color / mirror / Atom feed
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 319/327] arch/arm64/kvm/../../../virt/kvm/kvm_main.c:1979:12: warning: no previous prototype for function 'kvm_arch_required_alignment'
Date: Mon, 29 May 2023 21:11:51 +0800	[thread overview]
Message-ID: <202305292058.bSTEzaTY-lkp@intel.com> (raw)

tree:   https://github.com/intel/tdx.git kvm-upstream-workaround
head:   148ce77f987a3cf12193c1f81baa78f41cf13154
commit: f9628fde0c623c76992345cebbf4cefdcc6bb542 [319/327] KVM: Relax alignment check for restricted mem
config: arm64-buildonly-randconfig-r002-20230529 (https://download.01.org/0day-ci/archive/20230529/202305292058.bSTEzaTY-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 4faf3aaf28226a4e950c103a14f6fc1d1fdabb1b)
reproduce (this is a W=1 build):
        mkdir -p ~/bin
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/intel/tdx/commit/f9628fde0c623c76992345cebbf4cefdcc6bb542
        git remote add intel-tdx https://github.com/intel/tdx.git
        git fetch --no-tags intel-tdx kvm-upstream-workaround
        git checkout f9628fde0c623c76992345cebbf4cefdcc6bb542
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=arm64 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305292058.bSTEzaTY-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> arch/arm64/kvm/../../../virt/kvm/kvm_main.c:1981:19: error: expected ';' after return statement
           return PAGE_SHIFT
                            ^
                            ;
>> arch/arm64/kvm/../../../virt/kvm/kvm_main.c:1979:12: warning: no previous prototype for function 'kvm_arch_required_alignment' [-Wmissing-prototypes]
   __weak int kvm_arch_required_alignment(u64 gpa)
              ^
   arch/arm64/kvm/../../../virt/kvm/kvm_main.c:1979:8: note: declare 'static' if the function is not intended to be used outside of this translation unit
   __weak int kvm_arch_required_alignment(u64 gpa)
          ^
          static 
   1 warning and 1 error generated.


vim +/kvm_arch_required_alignment +1979 arch/arm64/kvm/../../../virt/kvm/kvm_main.c

  1977	
  1978	#ifndef kvm_arch_required_alignment
> 1979	__weak int kvm_arch_required_alignment(u64 gpa)
  1980	{
> 1981		return PAGE_SHIFT
  1982	}
  1983	#endif
  1984	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-05-29 13:12 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=202305292058.bSTEzaTY-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.