From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:rcu/dev 5/99] arch/x86/kernel/cpu/mtrr/main.c:797: undefined reference to `rcu_cpu_starting'
Date: Tue, 22 May 2018 15:08:18 -0700 [thread overview]
Message-ID: <20180522220818.GA3803@linux.vnet.ibm.com> (raw)
In-Reply-To: <201805230528.PpQTquMr%fengguang.wu@intel.com>
On Wed, May 23, 2018 at 05:30:30AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev
> head: 477fc1978395d58ae0406293a1d963629778a39d
> commit: 354238a30982b817262fe6f9d00f808451694366 [5/99] rcu/x86: Provide early rcu_cpu_starting() callback
> config: i386-randconfig-i1-201820 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> git checkout 354238a30982b817262fe6f9d00f808451694366
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
Problems with !SMP, which I am beating up on...
Thanx, Paul
> arch/x86/kernel/cpu/mtrr/main.o: In function `mtrr_ap_init':
> >> arch/x86/kernel/cpu/mtrr/main.c:797: undefined reference to `rcu_cpu_starting'
>
> vim +797 arch/x86/kernel/cpu/mtrr/main.c
>
> 788
> 789 void mtrr_ap_init(void)
> 790 {
> 791 if (!mtrr_enabled())
> 792 return;
> 793
> 794 if (!use_intel() || mtrr_aps_delayed_init)
> 795 return;
> 796
> > 797 rcu_cpu_starting(smp_processor_id());
> 798
> 799 /*
> 800 * Ideally we should hold mtrr_mutex here to avoid mtrr entries
> 801 * changed, but this routine will be called in cpu boot time,
> 802 * holding the lock breaks it.
> 803 *
> 804 * This routine is called in two cases:
> 805 *
> 806 * 1. very earily time of software resume, when there absolutely
> 807 * isn't mtrr entry changes;
> 808 *
> 809 * 2. cpu hotadd time. We let mtrr_add/del_page hold cpuhotplug
> 810 * lock to prevent mtrr entry changes
> 811 */
> 812 set_mtrr_from_inactive_cpu(~0U, 0, 0, 0);
> 813 }
> 814
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2018-05-22 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 21:30 [rcu:rcu/dev 5/99] arch/x86/kernel/cpu/mtrr/main.c:797: undefined reference to `rcu_cpu_starting' kbuild test robot
2018-05-22 22:08 ` Paul E. McKenney [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=20180522220818.GA3803@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.