From: kernel test robot <lkp@intel.com>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
Robert Hu <robert.hu@intel.com>,
Farrah Chen <farrah.chen@intel.com>,
Danmei Wei <danmei.wei@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Tony Luck <tony.luck@intel.com>
Subject: [kvm:nested-svm 79/95] arch/x86/kvm/vmx/vmx.c:5649:12: error: conflicting types for 'handle_bus_lock'
Date: Wed, 3 Feb 2021 06:06:50 +0800 [thread overview]
Message-ID: <202102030637.AGxHMTBj-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]
tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git nested-svm
head: 47fb7f6e83e4517e5b43345c1ee0c738263d933b
commit: a82a8fa7038222fd4ca556810c278871aa985a6e [79/95] x86/bus_lock: Handle warn and fatal in #DB for bus lock
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?id=a82a8fa7038222fd4ca556810c278871aa985a6e
git remote add kvm https://git.kernel.org/pub/scm/virt/kvm/kvm.git
git fetch --no-tags kvm nested-svm
git checkout a82a8fa7038222fd4ca556810c278871aa985a6e
# 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 errors (new ones prefixed by >>):
>> arch/x86/kvm/vmx/vmx.c:5649:12: error: conflicting types for 'handle_bus_lock'
5649 | static int handle_bus_lock(struct kvm_vcpu *vcpu)
| ^~~~~~~~~~~~~~~
In file included from arch/x86/kvm/vmx/vmx.c:34:
arch/x86/include/asm/cpu.h:48:13: note: previous declaration of 'handle_bus_lock' was here
48 | extern bool handle_bus_lock(struct pt_regs *regs);
| ^~~~~~~~~~~~~~~
vim +/handle_bus_lock +5649 arch/x86/kvm/vmx/vmx.c
e7953d7fab47a7 arch/x86/kvm/vmx.c Abel Gordon 2013-04-18 5648
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 @5649 static int handle_bus_lock(struct kvm_vcpu *vcpu)
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5650 {
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5651 vcpu->run->exit_reason = KVM_EXIT_X86_BUS_LOCK;
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5652 vcpu->run->flags |= KVM_RUN_X86_BUS_LOCK;
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5653 return 0;
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5654 }
1b054f0054cf1b arch/x86/kvm/vmx/vmx.c Chenyi Qiang 2020-11-06 5655
:::::: The code at line 5649 was first introduced by commit
:::::: 1b054f0054cf1bcd4979073e285c8ab53c331480 KVM: VMX: Enable bus lock VM exit
:::::: TO: Chenyi Qiang <chenyi.qiang@intel.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: 65025 bytes --]
next reply other threads:[~2021-02-02 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 22:06 kernel test robot [this message]
2021-02-03 7:41 ` [kvm:nested-svm 79/95] arch/x86/kvm/vmx/vmx.c:5649:12: error: conflicting types for 'handle_bus_lock' Paolo Bonzini
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=202102030637.AGxHMTBj-lkp@intel.com \
--to=lkp@intel.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@intel.com \
--cc=tony.luck@intel.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