From: kbuild test robot <lkp@intel.com>
To: Jingqi Liu <jingqi.liu@intel.com>
Cc: kbuild-all@01.org, pbonzini@redhat.com, rkrcmar@redhat.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, wei.w.wang@intel.com,
Jingqi Liu <jingqi.liu@intel.com>
Subject: Re: [PATCH 1/3] KVM: x86: expose UMWAIT/UMONITOR/TPAUSE CPU features into VM.
Date: Tue, 10 Jul 2018 20:12:36 +0800 [thread overview]
Message-ID: <201807101911.hk8WRtgK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1531212883-63173-2-git-send-email-jingqi.liu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
Hi Jingqi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on v4.18-rc4 next-20180709]
[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/Jingqi-Liu/KVM-x86-expose-a-few-new-features-into-VM/20180710-171958
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: x86_64-randconfig-s0-07101819 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/kvm/cpuid.c: In function '__do_cpuid_ent':
>> arch/x86/kvm/cpuid.c:68:18: error: 'X86_FEATURE_WAITPKG' undeclared (first use in this function)
#define F(x) bit(X86_FEATURE_##x)
^
arch/x86/kvm/cpuid.c:409:17: note: in expansion of macro 'F'
F(CLDEMOTE) | F(WAITPKG);
^
arch/x86/kvm/cpuid.c:68:18: note: each undeclared identifier is reported only once for each function it appears in
#define F(x) bit(X86_FEATURE_##x)
^
arch/x86/kvm/cpuid.c:409:17: note: in expansion of macro 'F'
F(CLDEMOTE) | F(WAITPKG);
^
vim +/X86_FEATURE_WAITPKG +68 arch/x86/kvm/cpuid.c
4ff41732 Paolo Bonzini 2014-02-24 67
5c404cab Paolo Bonzini 2014-12-03 @68 #define F(x) bit(X86_FEATURE_##x)
5c404cab Paolo Bonzini 2014-12-03 69
:::::: The code at line 68 was first introduced by commit
:::::: 5c404cabd1b5c125653ac573cb9284bdf42b658a KVM: x86: use F() macro throughout cpuid.c
:::::: TO: Paolo Bonzini <pbonzini@redhat.com>
:::::: CC: Paolo Bonzini <pbonzini@redhat.com>
---
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: 35138 bytes --]
next prev parent reply other threads:[~2018-07-10 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 8:54 [PATCH 0/3] KVM: x86: expose a few new features into VM Jingqi Liu
2018-07-10 8:54 ` [PATCH 1/3] KVM: x86: expose UMWAIT/UMONITOR/TPAUSE CPU " Jingqi Liu
2018-07-10 11:53 ` kbuild test robot
2018-07-10 12:12 ` kbuild test robot [this message]
2018-08-20 10:16 ` Paolo Bonzini
2018-08-20 12:36 ` Liu, Jingqi
2018-07-10 8:54 ` [PATCH 2/3] KVM: x86: expose MOVDIRI CPU feature " Jingqi Liu
2018-07-10 12:25 ` kbuild test robot
2018-07-10 8:54 ` [PATCH 3/3] KVM: x86: expose MOVDIR64B " Jingqi Liu
2018-07-10 10:04 ` kbuild test robot
2018-08-06 8:17 ` [PATCH 0/3] KVM: x86: expose a few new features " Liu, Jingqi
2018-08-06 16:58 ` 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=201807101911.hk8WRtgK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hpa@zytor.com \
--cc=jingqi.liu@intel.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=wei.w.wang@intel.com \
--cc=x86@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).