From: daniel.thompson@linaro•org (Daniel Thompson)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ
Date: Mon, 4 Jan 2016 10:00:36 +0000 [thread overview]
Message-ID: <568A42C4.4050106@linaro.org> (raw)
In-Reply-To: <201512210618.hMZqsBKl%fengguang.wu@intel.com>
On 20/12/15 22:12, kbuild test robot wrote:
> Hi Daniel,
>
> [auto build test ERROR on v4.4-rc5]
> [also build test ERROR on next-20151218]
> [cannot apply to tip/irq/core]
>
> url: https://github.com/0day-ci/linux/commits/Daniel-Thompson/irq-arm-Use-FIQ-for-NMI-backtrace-when-possible/20151221-045854
> config: arm-iop-adma (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> arch/arm/kernel/traps.c: In function 'handle_fiq_as_nmi':
>>> arch/arm/kernel/traps.c:489:2: error: implicit declaration of function 'handle_arch_irq' [-Werror=implicit-function-declaration]
> handle_arch_irq(regs);
> ^
> cc1: some warnings being treated as errors
Thanks. I'll look at this.
> vim +/handle_arch_irq +489 arch/arm/kernel/traps.c
>
> 483 * Either the interrupt controller supports FIQ, meaning it will
> 484 * do the right thing with this call, or we will end up treating a
> 485 * spurious FIQ (which is normally fatal) as though it were an IRQ
> 486 * which, although it risks deadlock, still gives us a sporting
> 487 * chance of surviving long enough to log errors.
> 488 */
> > 489 handle_arch_irq(regs);
> 490
> 491 nmi_exit();
> 492
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2016-01-04 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 20:52 [PATCH 4.4-rc5 v22 0/4] irq/arm: Use FIQ for NMI backtrace (when possible) Daniel Thompson
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 1/4] irqchip: gic: Optimize locking in gic_raise_softirq Daniel Thompson
2016-01-07 14:31 ` Marc Zyngier
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 2/4] irqchip: gic: Make gic_raise_softirq FIQ-safe Daniel Thompson
2016-01-07 14:35 ` Marc Zyngier
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 3/4] irqchip: gic: Introduce plumbing for IPI FIQ Daniel Thompson
2016-01-07 17:06 ` Marc Zyngier
2016-01-11 12:02 ` Daniel Thompson
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ Daniel Thompson
2015-12-20 22:12 ` kbuild test robot
2016-01-04 10:00 ` Daniel Thompson [this message]
2015-12-20 22:52 ` kbuild test robot
2016-01-04 10:05 ` Daniel Thompson
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=568A42C4.4050106@linaro.org \
--to=daniel.thompson@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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