From: kbuild test robot <lkp@intel.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Daniel Bristot de Oliveira <daniel@bristot.me>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Lutomirski <luto@kernel.org>,
Clark Williams <williams@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH 1/2] trace,x86: Add external_interrupts to the irq_vectors class
Date: Mon, 17 Sep 2018 18:24:08 +0800 [thread overview]
Message-ID: <201809171828.TLCEYwqL%fengguang.wu@intel.com> (raw)
In-Reply-To: <461ac057690a58e05395d07d0e1994855bb3cd7d.1537173660.git.bristot@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2744 bytes --]
Hi Daniel,
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-20180913]
[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/Daniel-Bristot-de-Oliveira/trace-x86-Add-external_interrupts-to-the-irq_vectors-class/20180917-173538
config: i386-randconfig-x003-201837 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/kernel/irq.c: In function 'do_IRQ':
>> arch/x86/kernel/irq.c:240:2: error: implicit declaration of function 'trace_external_interrupt_entry'; did you mean 'thermal_interrupt'? [-Werror=implicit-function-declaration]
trace_external_interrupt_entry(vector);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
thermal_interrupt
>> arch/x86/kernel/irq.c:259:2: error: implicit declaration of function 'trace_external_interrupt_exit'; did you mean 'thermal_interrupt'? [-Werror=implicit-function-declaration]
trace_external_interrupt_exit(vector);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
thermal_interrupt
cc1: some warnings being treated as errors
vim +240 arch/x86/kernel/irq.c
225
226
227 /*
228 * do_IRQ handles all normal device IRQ's (the special
229 * SMP cross-CPU interrupts have their own specific
230 * handlers).
231 */
232 __visible unsigned int __irq_entry do_IRQ(struct pt_regs *regs)
233 {
234 struct pt_regs *old_regs = set_irq_regs(regs);
235 struct irq_desc * desc;
236 /* high bit used in ret_from_ code */
237 unsigned vector = ~regs->orig_ax;
238
239 entering_irq();
> 240 trace_external_interrupt_entry(vector);
241
242 /* entering_irq() tells RCU that we're not quiescent. Check it. */
243 RCU_LOCKDEP_WARN(!rcu_is_watching(), "IRQ failed to wake up RCU");
244
245 desc = __this_cpu_read(vector_irq[vector]);
246
247 if (!handle_irq(desc, regs)) {
248 ack_APIC_irq();
249
250 if (desc != VECTOR_RETRIGGERED) {
251 pr_emerg_ratelimited("%s: %d.%d No irq handler for vector\n",
252 __func__, smp_processor_id(),
253 vector);
254 } else {
255 __this_cpu_write(vector_irq[vector], VECTOR_UNUSED);
256 }
257 }
258
> 259 trace_external_interrupt_exit(vector);
260 exiting_irq();
261
262 set_irq_regs(old_regs);
263 return 1;
264 }
265
---
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: 22639 bytes --]
prev parent reply other threads:[~2018-09-17 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 8:48 Daniel Bristot de Oliveira
2018-09-17 8:48 ` [PATCH 2/2] trace,x86: Add nmi " Daniel Bristot de Oliveira
2018-09-17 10:18 ` kbuild test robot
2018-09-17 10:24 ` 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=201809171828.TLCEYwqL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bristot@redhat.com \
--cc=daniel@bristot.me \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@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
all inboxes | Powered by JetHome®