linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12154/12271] tools/testing/selftests/kvm/x86_64/hyperv_features.c:618: undefined reference to `vm_handle_exception'
Date: Wed, 23 Jun 2021 06:54:17 +0800	[thread overview]
Message-ID: <202106230606.sNbagz4E-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4351 bytes --]

Hi Stephen,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   4238b1710eadd18dd16de0288a2bc5bb84614b4e
commit: 954e285eafdd4ac36b114a7f6abce3f792591ea8 [12154/12271] Merge remote-tracking branch 'kvm-arm/next'
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=954e285eafdd4ac36b114a7f6abce3f792591ea8
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 954e285eafdd4ac36b114a7f6abce3f792591ea8
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

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

   x86_64/hyperv_features.c: In function 'main':
>> x86_64/hyperv_features.c:618:2: warning: implicit declaration of function 'vm_handle_exception' [-Wimplicit-function-declaration]
     618 |  vm_handle_exception(vm, GP_VECTOR, guest_gp_handler);
         |  ^~~~~~~~~~~~~~~~~~~
   /usr/bin/ld: /tmp/ccIBsVo3.o: in function `main':
>> tools/testing/selftests/kvm/x86_64/hyperv_features.c:618: undefined reference to `vm_handle_exception'
   collect2: error: ld returned 1 exit status
--
   x86_64/hyperv_features.c: In function 'main':
>> x86_64/hyperv_features.c:618:2: warning: implicit declaration of function 'vm_handle_exception' [-Wimplicit-function-declaration]
     618 |  vm_handle_exception(vm, GP_VECTOR, guest_gp_handler);
         |  ^~~~~~~~~~~~~~~~~~~
   /usr/bin/ld: /tmp/cc7zqGvp.o: in function `main':
>> tools/testing/selftests/kvm/x86_64/hyperv_features.c:618: undefined reference to `vm_handle_exception'
   collect2: error: ld returned 1 exit status


vim +618 tools/testing/selftests/kvm/x86_64/hyperv_features.c

e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  593  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  594  int main(void)
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  595  {
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  596  	struct kvm_cpuid2 *best;
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  597  	struct kvm_vm *vm;
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  598  	vm_vaddr_t msr_gva, hcall_page, hcall_params;
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  599  	struct kvm_enable_cap cap = {
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  600  		.cap = KVM_CAP_HYPERV_ENFORCE_CPUID,
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  601  		.args = {1}
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  602  	};
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  603  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  604  	/* Test MSRs */
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  605  	vm = vm_create_default(VCPU_ID, 0, guest_msr);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  606  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  607  	msr_gva = vm_vaddr_alloc(vm, getpagesize(), 0x10000, 0, 0);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  608  	memset(addr_gva2hva(vm, msr_gva), 0x0, getpagesize());
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  609  	vcpu_args_set(vm, VCPU_ID, 1, msr_gva);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  610  	vcpu_enable_cap(vm, VCPU_ID, &cap);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  611  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  612  	vcpu_set_hv_cpuid(vm, VCPU_ID);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  613  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  614  	best = kvm_get_supported_hv_cpuid();
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  615  
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  616  	vm_init_descriptor_tables(vm);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21  617  	vcpu_init_descriptor_tables(vm, VCPU_ID);
e2e1cc1fbe54a9 Vitaly Kuznetsov 2021-05-21 @618  	vm_handle_exception(vm, GP_VECTOR, guest_gp_handler);

:::::: The code at line 618 was first introduced by commit
:::::: e2e1cc1fbe54a9520956a4539a3676d2ebf122dd KVM: selftests: Introduce hyperv_features test

:::::: TO: Vitaly Kuznetsov <vkuznets@redhat.com>
:::::: CC: Paolo Bonzini <pbonzini@redhat.com>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42038 bytes --]

             reply	other threads:[~2021-06-22 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 22:54 kernel test robot [this message]
2021-06-23  7:59 ` [linux-next:master 12154/12271] tools/testing/selftests/kvm/x86_64/hyperv_features.c:618: undefined reference to `vm_handle_exception' Marc Zyngier
2021-06-23  8:39   ` Paolo Bonzini
2021-06-24  1:01   ` Ricardo Koller

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=202106230606.sNbagz4E-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=maz@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).