From: kbuild test robot <lkp@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, rkrcmar@redhat.com, dmatlack@google.com,
luto@kernel.org, peterhornyack@google.com, x86@kernel.org
Subject: Re: [PATCH 1/2] x86: paravirt: add local_apic_timer_interrupt to pv_ops
Date: Wed, 7 Sep 2016 14:33:01 +0800 [thread overview]
Message-ID: <201609071409.EKAyxzGz%fengguang.wu@intel.com> (raw)
In-Reply-To: <1473200999-123004-2-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
Hi Paolo,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.8-rc5 next-20160906]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Paolo-Bonzini/if-running-under-KVM-use-kvmclock-to-compute-TSC-deadline-value/20160907-131553
config: i386-randconfig-s1-201636 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> arch/x86/kernel/paravirt.c:313:32: error: 'native_local_apic_timer_interrupt' undeclared here (not in a function)
.local_apic_timer_interrupt = native_local_apic_timer_interrupt,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/native_local_apic_timer_interrupt +313 arch/x86/kernel/paravirt.c
307 .patch = native_patch,
308 };
309
310 struct pv_time_ops pv_time_ops = {
311 .sched_clock = native_sched_clock,
312 .steal_clock = native_steal_clock,
> 313 .local_apic_timer_interrupt = native_local_apic_timer_interrupt,
314 };
315
316 __visible struct pv_irq_ops pv_irq_ops = {
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26872 bytes --]
next prev parent reply other threads:[~2016-09-07 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 22:29 [PATCH v2 0/2] if running under KVM, use kvmclock to compute TSC deadline value Paolo Bonzini
2016-09-06 22:29 ` [PATCH 1/2] x86: paravirt: add local_apic_timer_interrupt to pv_ops Paolo Bonzini
2016-09-07 6:25 ` kbuild test robot
2016-09-07 6:33 ` kbuild test robot [this message]
2016-09-06 22:29 ` [PATCH 2/2] x86, kvm: use kvmclock to compute TSC deadline value Paolo Bonzini
2016-09-08 22:13 ` David Matlack
2016-09-09 16:38 ` Paolo Bonzini
2016-09-09 20:05 ` David Matlack
2016-10-11 4:05 ` Wanpeng Li
2016-09-15 15:09 ` Radim Krčmář
2016-09-15 16:00 ` Paolo Bonzini
2016-09-15 19:59 ` Radim Krčmář
2016-09-15 21:02 ` Paolo Bonzini
2016-09-16 14:59 ` Radim Krčmář
2016-09-16 15:06 ` Paolo Bonzini
2016-09-16 15:24 ` Radim Krčmář
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=201609071409.EKAyxzGz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dmatlack@google.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterhornyack@google.com \
--cc=rkrcmar@redhat.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).