From: kbuild test robot <lkp@intel.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
Radim =?unknown-8bit?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Sean Christopherson" <sean.j.christopherson@intel.com>,
"Nadav Amit" <namit@vmware.com>
Subject: Re: [PATCH] KVM: X86: Use IPI shorthands in kvm guest when support
Date: Sat, 27 Jul 2019 01:22:31 +0800 [thread overview]
Message-ID: <201907270129.hfIBA014%lkp@intel.com> (raw)
In-Reply-To: <1564121417-29375-1-git-send-email-wanpengli@tencent.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi Wanpeng,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc1 next-20190726]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Wanpeng-Li/KVM-X86-Use-IPI-shorthands-in-kvm-guest-when-support/20190726-201453
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ld: arch/x86/kernel/kvm.o:(__jump_table+0x8): undefined reference to `apic_use_ipi_shorthand'
ld: arch/x86/kernel/kvm.o:(__jump_table+0x18): undefined reference to `apic_use_ipi_shorthand'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 43523 bytes --]
prev parent reply other threads:[~2019-07-26 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:10 Wanpeng Li
2019-07-26 6:16 ` Wanpeng Li
2019-07-26 7:20 ` Thomas Gleixner
2019-07-26 7:46 ` Wanpeng Li
2019-07-26 17:22 ` kbuild test robot [this message]
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=201907270129.hfIBA014%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®