mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Prarit Bhargava <prarit@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Rui Wang <rui.y.wang@intel.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Borislav Petkov <bp@suse.de>, Aaron Lu <aaron.lu@intel.com>
Subject: Re: [PATCH] x86/irq: Add additional unhandled IRQ debug information
Date: Wed, 7 Dec 2016 02:41:21 +0800	[thread overview]
Message-ID: <201612070230.MWoCjcOL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481039448-31746-1-git-send-email-prarit@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3864 bytes --]

Hi Prarit,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.9-rc8 next-20161206]
[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/Prarit-Bhargava/x86-irq-Add-additional-unhandled-IRQ-debug-information/20161207-022400
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All error/warnings (new ones prefixed by >>):

   In file included from arch/x86/kernel/irq.c:16:0:
>> arch/x86/include/asm/io_apic.h:207:15: warning: return type defaults to 'int' [-Wreturn-type]
    static inline print_IRQ_to_pin_mapping(unsigned int irq) {}
                  ^~~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/linux/kobject.h:29:0,
                    from include/linux/device.h:17,
                    from include/linux/node.h:17,
                    from include/linux/cpu.h:16,
                    from arch/x86/kernel/irq.c:4:
   arch/x86/kernel/irq.c: In function 'arch_irq_debug':
>> arch/x86/kernel/irq.c:584:13: error: 'x86_unhandled_irq_work' undeclared (first use in this function)
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
                ^
   include/linux/workqueue.h:216:16: note: in definition of macro '__INIT_WORK'
      __init_work((_work), _onstack);    \
                   ^~~~~
   arch/x86/kernel/irq.c:584:2: note: in expansion of macro 'INIT_WORK'
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
     ^~~~~~~~~
   arch/x86/kernel/irq.c:584:13: note: each undeclared identifier is reported only once for each function it appears in
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
                ^
   include/linux/workqueue.h:216:16: note: in definition of macro '__INIT_WORK'
      __init_work((_work), _onstack);    \
                   ^~~~~
   arch/x86/kernel/irq.c:584:2: note: in expansion of macro 'INIT_WORK'
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
     ^~~~~~~~~
>> arch/x86/kernel/irq.c:584:37: error: 'x86_unhandled_irq_work_fn' undeclared (first use in this function)
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
                                        ^
   include/linux/workqueue.h:219:20: note: in definition of macro '__INIT_WORK'
      (_work)->func = (_func);    \
                       ^~~~~
   arch/x86/kernel/irq.c:584:2: note: in expansion of macro 'INIT_WORK'
     INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
     ^~~~~~~~~
   arch/x86/kernel/irq.c:579:6: warning: unused variable 'reg' [-Wunused-variable]
     u32 reg;
         ^~~
   arch/x86/kernel/irq.c:578:11: warning: unused variable 'bit' [-Wunused-variable]
     int irr, bit;
              ^~~
   arch/x86/kernel/irq.c:578:6: warning: unused variable 'irr' [-Wunused-variable]
     int irr, bit;
         ^~~
--
   In file included from arch/x86/kernel/setup.c:85:0:
>> arch/x86/include/asm/io_apic.h:207:15: warning: return type defaults to 'int' [-Wreturn-type]
    static inline print_IRQ_to_pin_mapping(unsigned int irq) {}
                  ^~~~~~~~~~~~~~~~~~~~~~~~

vim +/x86_unhandled_irq_work +584 arch/x86/kernel/irq.c

   578		int irr, bit;
   579		u32 reg;
   580	
   581		pr_emerg("Additional x86 information on IRQ #%d ...\n", irq);
   582	
   583		/* PCI information cannot be dumped in interrupt context */
 > 584		INIT_WORK(&x86_unhandled_irq_work, x86_unhandled_irq_work_fn);
   585		schedule_work_on(smp_processor_id(), &x86_unhandled_irq_work);
   586	
   587	#ifdef CONFIG_X86_IO_APIC

---
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: 6363 bytes --]

      reply	other threads:[~2016-12-06 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 15:50 Prarit Bhargava
2016-12-06 18:41 ` 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=201612070230.MWoCjcOL%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=aaron.lu@intel.com \
    --cc=bp@suse.de \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=prarit@redhat.com \
    --cc=rui.y.wang@intel.com \
    --cc=tglx@linutronix.de \
    --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®