xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: WARNING: at /home/konrad/linux-linus/kernel/time/tick-sched.c:935 tick_nohz_idle_exit+0x195/0x1b0() on v3.10-rc3
Date: Thu, 30 May 2013 22:05:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1305302152410.2905@ionos> (raw)
In-Reply-To: <20130530182948.GA11612@phenom.dumpdata.com>

On Thu, 30 May 2013, Konrad Rzeszutek Wilk wrote:
> [   40.085841] WARNING: at /home/konrad/linux-linus/kernel/time/tick-sched.c:935 tick_nohz_idle_exit+0x195/0x1b0()
> 
> which I presume is b/c the code does not expect to be run _after_ it has
> offlined. However, under the PV code, the mechanism is that that a CPU
> that has been offlined, can resume (if it is onlined). If you look at:
> 
> 445 static void __cpuinit xen_play_dead(void) /* used only with HOTPLUG_CPU */      
> 446 {                                                                               
> 447         play_dead_common();                                                     
> 448         HYPERVISOR_vcpu_op(VCPUOP_down, smp_processor_id(), NULL);              
> 449         cpu_bringup();                                                          
> 450 }                               
> 
> That is called right after the CPU is put to sleep and the hypercall 
> VCPUOP_down blocks - until the CPU is brough back up. And which point
> we end up calling cpu_bringup - which sets up the clockevets, timers, etc.
>
> I am wondering if part of this is that the ts->inidle gets reset
> b/c we end up resetting all the timers but then when xen_play_dead
> exits, it ends up right back in the cpu_idle_loop() loop - and we
> call tick_nohz_idle_exit().
> 
> Thoughts?

cpu_dead() is definitely not expected to return after the cpu has been
declared dead. I should have put a big fat warning into the generic
idle loop for this :)

The reason why you get that warning only now is commit 4b0c0f294
(tick: Cleanup NOHZ per cpu data on cpu down), which is btw. targeted
for stable as well.

We can't revert the above commit as it fixes a long standing
nastiness, so for now until I come around to make the idle loop return
on cpu down you probably need to call tick_nohz_idle_enter() before
returning from play_dead().

Thanks,

	tglx



    

  reply	other threads:[~2013-05-30 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 18:29 WARNING: at /home/konrad/linux-linus/kernel/time/tick-sched.c:935 tick_nohz_idle_exit+0x195/0x1b0() on v3.10-rc3 Konrad Rzeszutek Wilk
2013-05-30 20:05 ` Thomas Gleixner [this message]
2013-06-03 13:42   ` Konrad Rzeszutek Wilk

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=alpine.LFD.2.02.1305302152410.2905@ionos \
    --to=tglx@linutronix.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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).