kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "lkp@intel.com" <lkp@intel.com>
Cc: "fenghua.yu@intel.com" <fenghua.yu@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"Izumi, Taku" <izumi.taku@jp.fujitsu.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"kbuild-all@01.org" <kbuild-all@01.org>
Subject: Re: [PATCH] kexec: Fix kdump failure with notsc
Date: Thu, 7 Jul 2016 10:26:47 +0000	[thread overview]
Message-ID: <1467887078.2119.63.camel@localhost> (raw)
In-Reply-To: <201607071617.dgK52iri%fengguang.wu@intel.com>

Hi all,

I fixed the compile error and sent the v2.
Please ignore this serial.

Thanks,
wei

On Thu, 2016-07-07 at 16:46 +0800, kbuild test robot wrote:
> Hi,
> 
> [auto build test ERROR on tip/x86/core]
> [also build test ERROR on v4.7-rc6 next-20160706]
> [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/Wei-Jiangang/kexec-Fix-kdump-failure-with-notsc/20160707-152535
> config: x86_64-randconfig-s5-07071541 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> All errors (new ones prefixed by >>):
> 
>    arch/x86/kernel/machine_kexec_64.c: In function 'machine_kexec':
> >> arch/x86/kernel/machine_kexec_64.c:272:33: error: implicit declaration of function 'lapic_disabled' [-Werror=implicit-function-declaration]
>      if (image->preserve_context || lapic_disabled()) {
>                                     ^~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/lapic_disabled +272 arch/x86/kernel/machine_kexec_64.c
> 
>    266		save_ftrace_enabled = __ftrace_enabled_save();
>    267	
>    268		/* Interrupts aren't acceptable while we reboot */
>    269		local_irq_disable();
>    270		hw_breakpoint_disable();
>    271	
>  > 272		if (image->preserve_context || lapic_disabled()) {
>    273	#ifdef CONFIG_X86_IO_APIC
>    274			/*
>    275			 * We need to put APICs in legacy mode so that we can
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> 
> 



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2016-07-07 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  7:20 [PATCH] kexec: Fix kdump failure with notsc Wei Jiangang
2016-07-07  8:46 ` kbuild test robot
2016-07-07 10:26   ` Wei, Jiangang [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=1467887078.2119.63.camel@localhost \
    --to=weijg.fnst@cn.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kbuild-all@01.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).