From: kbuild test robot <lkp@intel.com>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Borislav Petkov <bp@suse.de>,
Jason Chen CJ <jason.cj.chen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [tip:WIP.x86/core 28/29] arch/x86/kernel/cpu/acrn.c:52:2: error: implicit declaration of function 'entering_ack_irq'; did you mean 'spin_lock_irq'?
Date: Tue, 28 May 2019 05:50:48 +0800 [thread overview]
Message-ID: <201905280546.eSrcufDM%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/core
head: 830be9dae84c3a781f6d1594c4038c164bbae52b
commit: 6fc278e883365e67dd4a35e25b756d9d0c9d913c [28/29] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector
config: x86_64-randconfig-s505280430 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 6fc278e883365e67dd4a35e25b756d9d0c9d913c
# 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 >>):
arch/x86/kernel/cpu/acrn.c: In function 'acrn_hv_vector_handler':
>> arch/x86/kernel/cpu/acrn.c:52:2: error: implicit declaration of function 'entering_ack_irq'; did you mean 'spin_lock_irq'? [-Werror=implicit-function-declaration]
entering_ack_irq();
^~~~~~~~~~~~~~~~
spin_lock_irq
>> arch/x86/kernel/cpu/acrn.c:58:2: error: implicit declaration of function 'exiting_irq'; did you mean 'in_irq'? [-Werror=implicit-function-declaration]
exiting_irq();
^~~~~~~~~~~
in_irq
cc1: some warnings being treated as errors
vim +52 arch/x86/kernel/cpu/acrn.c
40
41 __visible void __irq_entry acrn_hv_vector_handler(struct pt_regs *regs)
42 {
43 struct pt_regs *old_regs = set_irq_regs(regs);
44
45 /*
46 * The hypervisor requires that the APIC EOI should be acked.
47 * If the APIC EOI is not acked, the APIC ISR bit for the
48 * HYPERVISOR_CALLBACK_VECTOR will not be cleared and then it
49 * will block the interrupt whose vector is lower than
50 * HYPERVISOR_CALLBACK_VECTOR.
51 */
> 52 entering_ack_irq();
53 inc_irq_stat(irq_hv_callback_count);
54
55 if (acrn_intr_handler)
56 acrn_intr_handler();
57
> 58 exiting_irq();
59 set_irq_regs(old_regs);
60 }
61
---
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: 30519 bytes --]
reply other threads:[~2019-05-27 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201905280546.eSrcufDM%lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=jason.cj.chen@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
--cc=yakui.zhao@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