From: kbuild test robot <lkp@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: kbuild-all@01.org, x86@kernel.org, devel@linuxdriverproject.org,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic
Date: Thu, 1 Dec 2016 19:36:33 +0800 [thread overview]
Message-ID: <201612011938.bzQzFmh8%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161130175514.31416-1-vkuznets@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Hi Vitaly,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.9-rc7 next-20161130]
[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/Vitaly-Kuznetsov/x86-hyperv-Handle-unknown-NMIs-on-one-CPU-when-unknown_nmi_panic/20161201-171219
config: i386-randconfig-x014-201648 (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 errors (new ones prefixed by >>):
arch/x86/kernel/cpu/mshyperv.c: In function 'hv_nmi_unknown':
>> arch/x86/kernel/cpu/mshyperv.c:171:7: error: 'unknown_nmi_panic' undeclared (first use in this function)
if (!unknown_nmi_panic)
^~~~~~~~~~~~~~~~~
arch/x86/kernel/cpu/mshyperv.c:171:7: note: each undeclared identifier is reported only once for each function it appears in
vim +/unknown_nmi_panic +171 arch/x86/kernel/cpu/mshyperv.c
165 * unknown NMI on the first CPU which gets it.
166 */
167 static int hv_nmi_unknown(unsigned int val, struct pt_regs *regs)
168 {
169 static atomic_t nmi_cpu = ATOMIC_INIT(-1);
170
> 171 if (!unknown_nmi_panic)
172 return NMI_DONE;
173
174 if (atomic_cmpxchg(&nmi_cpu, -1, raw_smp_processor_id()) != -1)
---
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: 24405 bytes --]
next prev parent reply other threads:[~2016-12-01 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 17:55 Vitaly Kuznetsov
2016-11-30 19:30 ` KY Srinivasan
2016-12-01 11:36 ` kbuild test robot [this message]
2016-12-01 13:01 ` kbuild test robot
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=201612011938.bzQzFmh8%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@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®