linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [rcu:dev.2019.07.31a 56/123] arch/x86//xen/smp_pv.c:437:2: error: implicit declaration of function 'tick_nohz_idle_stop_tick_protected'; did you mean 'tick_nohz_idle_stop_tick'?
@ 2019-08-07 20:15 kbuild test robot
  0 siblings, 0 replies; only message in thread
From: kbuild test robot @ 2019-08-07 20:15 UTC (permalink / raw)
  To: Peter Zijlstra; +Cc: kbuild-all, linux-kernel, Paul E. McKenney

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.07.31a
head:   71cf692f482ff45802352cf85a8880035fca9e52
commit: ca9c8c15d1dbfadb846a267e0bb88f1e2aee882a [56/123] idle: Prevent late-arriving interrupts from disrupting offline
config: x86_64-randconfig-e002-201931 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
        git checkout ca9c8c15d1dbfadb846a267e0bb88f1e2aee882a
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/x86//xen/smp_pv.c: In function 'xen_pv_play_dead':
>> arch/x86//xen/smp_pv.c:437:2: error: implicit declaration of function 'tick_nohz_idle_stop_tick_protected'; did you mean 'tick_nohz_idle_stop_tick'? [-Werror=implicit-function-declaration]
     tick_nohz_idle_stop_tick_protected();
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     tick_nohz_idle_stop_tick
   cc1: some warnings being treated as errors

vim +437 arch/x86//xen/smp_pv.c

83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  424  
8cb6de390096b2 Vitaly Kuznetsov  2017-03-14  425  static void xen_pv_play_dead(void) /* used only with HOTPLUG_CPU */
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  426  {
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  427  	play_dead_common();
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  428  	HYPERVISOR_vcpu_op(VCPUOP_down, xen_vcpu_nr(smp_processor_id()), NULL);
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  429  	cpu_bringup();
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  430  	/*
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  431  	 * commit 4b0c0f294 (tick: Cleanup NOHZ per cpu data on cpu down)
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  432  	 * clears certain data that the cpu_idle loop (which called us
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  433  	 * and that we return from) expects. The only way to get that
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  434  	 * data back is to call:
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  435  	 */
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  436  	tick_nohz_idle_enter();
0e7767687fdabf Rafael J. Wysocki 2018-04-05 @437  	tick_nohz_idle_stop_tick_protected();
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  438  
c185ddec54657c Juergen Gross     2017-07-05  439  	cpuhp_online_idle(CPUHP_AP_ONLINE_IDLE);
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  440  }
83b96794e0ea97 Vitaly Kuznetsov  2017-03-14  441  

:::::: The code at line 437 was first introduced by commit
:::::: 0e7767687fdabfc58d5046e7488632bf2ecd4d0c time: tick-sched: Reorganize idle tick management code

:::::: TO: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-08-07 20:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-07 20:15 [rcu:dev.2019.07.31a 56/123] arch/x86//xen/smp_pv.c:437:2: error: implicit declaration of function 'tick_nohz_idle_stop_tick_protected'; did you mean 'tick_nohz_idle_stop_tick'? kbuild test robot

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).