From: kbuild test robot <lkp@intel.com>
To: Yi Sun <yi.y.sun@linux.intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, x86@kernel.org,
tglx@linutronix.de, chao.p.peng@intel.com, chao.gao@intel.com,
isaku.yamahata@intel.com, michael.h.kelley@microsoft.com,
tianyu.lan@microsoft.com, Yi Sun <yi.y.sun@linux.intel.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH v2 2/2] locking/pvqspinlock, hv: Enable PV qspinlock for Hyper-V
Date: Sat, 22 Sep 2018 03:09:54 +0800 [thread overview]
Message-ID: <201809220343.NptFCXnT%fengguang.wu@intel.com> (raw)
In-Reply-To: <1537514712-62434-3-git-send-email-yi.y.sun@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]
Hi Yi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.19-rc4 next-20180921]
[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/Yi-Sun/Enable-PV-qspinlock-for-Hyper-V/20180921-234519
config: x86_64-randconfig-s1-09212334 (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/kernel/cpu/mshyperv.o: In function `hv_init_spinlocks':
>> arch/x86/include/asm/mshyperv.h:373: multiple definition of `hv_init_spinlocks'
arch/x86/entry/vdso/vma.o:arch/x86/include/asm/mshyperv.h:373: first defined here
vim +373 arch/x86/include/asm/mshyperv.h
359
360 #else /* CONFIG_HYPERV */
361 static inline void hyperv_init(void) {}
362 static inline bool hv_is_hyperv_initialized(void) { return false; }
363 static inline void hyperv_cleanup(void) {}
364 static inline void hyperv_setup_mmu_ops(void) {}
365 static inline void set_hv_tscchange_cb(void (*cb)(void)) {}
366 static inline void clear_hv_tscchange_cb(void) {}
367 static inline void hyperv_stop_tsc_emulation(void) {};
368 static inline struct hv_vp_assist_page *hv_get_vp_assist_page(unsigned int cpu)
369 {
370 return NULL;
371 }
372 static inline int hyperv_flush_guest_mapping(u64 as) { return -1; }
> 373 void __init hv_init_spinlocks(void) {}
374 #endif /* CONFIG_HYPERV */
375
---
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: 31145 bytes --]
next prev parent reply other threads:[~2018-09-21 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 7:25 [PATCH v2 0/2] " Yi Sun
2018-09-21 7:25 ` [PATCH v2 1/2] X86/Hyper-V: Add Guest IDLE MSR support Yi Sun
2018-09-21 16:52 ` Michael Kelley (EOSG)
2018-09-21 7:25 ` [PATCH v2 2/2] locking/pvqspinlock, hv: Enable PV qspinlock for Hyper-V Yi Sun
2018-09-21 17:02 ` Michael Kelley (EOSG)
2018-09-25 7:11 ` Yi Sun
2018-09-21 19:09 ` kbuild test robot [this message]
2018-09-26 2:15 ` kbuild test robot
2018-09-26 8:23 ` Thomas Gleixner
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=201809220343.NptFCXnT%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@intel.com \
--cc=haiyangz@microsoft.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@01.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.h.kelley@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=tianyu.lan@microsoft.com \
--cc=x86@kernel.org \
--cc=yi.y.sun@linux.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
all inboxes | Powered by JetHome®