Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Fuad Tabba <tabba@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v9 14/17] KVM: arm64: Enable mapping guest_memfd in arm64
Date: Wed, 14 May 2025 13:44:19 +0800	[thread overview]
Message-ID: <202505141338.1SqLzH12-lkp@intel.com> (raw)
In-Reply-To: <20250513163438.3942405-15-tabba@google.com>

Hi Fuad,

kernel test robot noticed the following build errors:

[auto build test ERROR on 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3]

url:    https://github.com/intel-lab-lkp/linux/commits/Fuad-Tabba/KVM-Rename-CONFIG_KVM_PRIVATE_MEM-to-CONFIG_KVM_GMEM/20250514-003900
base:   82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3
patch link:    https://lore.kernel.org/r/20250513163438.3942405-15-tabba%40google.com
patch subject: [PATCH v9 14/17] KVM: arm64: Enable mapping guest_memfd in arm64
config: arm64-randconfig-004-20250514 (https://download.01.org/0day-ci/archive/20250514/202505141338.1SqLzH12-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250514/202505141338.1SqLzH12-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/202505141338.1SqLzH12-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/arm64/kernel/asm-offsets.c:15:
>> include/linux/kvm_host.h:726:20: error: redefinition of 'kvm_arch_supports_gmem'
     726 | static inline bool kvm_arch_supports_gmem(struct kvm *kvm)
         |                    ^
   arch/arm64/include/asm/kvm_host.h:1596:20: note: previous definition is here
    1596 | static inline bool kvm_arch_supports_gmem(struct kvm *kvm)
         |                    ^
   In file included from arch/arm64/kernel/asm-offsets.c:15:
>> include/linux/kvm_host.h:739:20: error: redefinition of 'kvm_arch_vm_supports_gmem_shared_mem'
     739 | static inline bool kvm_arch_vm_supports_gmem_shared_mem(struct kvm *kvm)
         |                    ^
   arch/arm64/include/asm/kvm_host.h:1601:20: note: previous definition is here
    1601 | static inline bool kvm_arch_vm_supports_gmem_shared_mem(struct kvm *kvm)
         |                    ^
   2 errors generated.
   make[3]: *** [scripts/Makefile.build:98: arch/arm64/kernel/asm-offsets.s] Error 1 shuffle=2236105568
   make[3]: Target 'prepare' not remade because of errors.
   make[2]: *** [Makefile:1275: prepare0] Error 2 shuffle=2236105568
   make[2]: Target 'prepare' not remade because of errors.
   make[1]: *** [Makefile:248: __sub-make] Error 2 shuffle=2236105568
   make[1]: Target 'prepare' not remade because of errors.
   make: *** [Makefile:248: __sub-make] Error 2 shuffle=2236105568
   make: Target 'prepare' not remade because of errors.


vim +/kvm_arch_supports_gmem +726 include/linux/kvm_host.h

f481b069e67437 Paolo Bonzini       2015-05-17  720  
a7800aa80ea4d5 Sean Christopherson 2023-11-13  721  /*
fc8463899419fd Fuad Tabba          2025-05-13  722   * Arch code must define kvm_arch_supports_gmem if support for guest_memfd
a7800aa80ea4d5 Sean Christopherson 2023-11-13  723   * is enabled.
a7800aa80ea4d5 Sean Christopherson 2023-11-13  724   */
fc8463899419fd Fuad Tabba          2025-05-13  725  #if !defined(kvm_arch_supports_gmem) && !IS_ENABLED(CONFIG_KVM_GMEM)
fc8463899419fd Fuad Tabba          2025-05-13 @726  static inline bool kvm_arch_supports_gmem(struct kvm *kvm)
a7800aa80ea4d5 Sean Christopherson 2023-11-13  727  {
a7800aa80ea4d5 Sean Christopherson 2023-11-13  728  	return false;
a7800aa80ea4d5 Sean Christopherson 2023-11-13  729  }
a7800aa80ea4d5 Sean Christopherson 2023-11-13  730  #endif
a7800aa80ea4d5 Sean Christopherson 2023-11-13  731  
33a8543055465e Fuad Tabba          2025-05-13  732  /*
33a8543055465e Fuad Tabba          2025-05-13  733   * Returns true if this VM supports shared mem in guest_memfd.
33a8543055465e Fuad Tabba          2025-05-13  734   *
33a8543055465e Fuad Tabba          2025-05-13  735   * Arch code must define kvm_arch_vm_supports_gmem_shared_mem if support for
33a8543055465e Fuad Tabba          2025-05-13  736   * guest_memfd is enabled.
33a8543055465e Fuad Tabba          2025-05-13  737   */
33a8543055465e Fuad Tabba          2025-05-13  738  #if !defined(kvm_arch_vm_supports_gmem_shared_mem) && !IS_ENABLED(CONFIG_KVM_GMEM)
33a8543055465e Fuad Tabba          2025-05-13 @739  static inline bool kvm_arch_vm_supports_gmem_shared_mem(struct kvm *kvm)
33a8543055465e Fuad Tabba          2025-05-13  740  {
33a8543055465e Fuad Tabba          2025-05-13  741  	return false;
33a8543055465e Fuad Tabba          2025-05-13  742  }
33a8543055465e Fuad Tabba          2025-05-13  743  #endif
33a8543055465e Fuad Tabba          2025-05-13  744  

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

           reply	other threads:[~2025-05-14  5:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250513163438.3942405-15-tabba@google.com>]

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=202505141338.1SqLzH12-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tabba@google.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