lkml.org 
[lkml]   [2015]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: clockevents_shutdown vs pending interrupt
On Tue, 23 Jun 2015, Andriy Gapon wrote:
> Pardon if I am asking something obvious or silly...
>
> tick_check_new_device() has the following code:
>
> if (tick_is_broadcast_device(curdev)) {
> clockevents_shutdown(curdev);
> curdev = NULL;
> }
>
> and
>
> void clockevents_shutdown(struct clock_event_device *dev)
> {
> clockevents_set_mode(dev, CLOCK_EVT_MODE_SHUTDOWN);
> dev->next_event.tv64 = KTIME_MAX;
> }
>
> This is all done while interrupts are disabled on the current CPU.
> But what if there is already a pending interrupt from the current source?
> Is it possible that the timer interrupt would be processed by the device that
> was put in the shutdown mode?
>
> Some context: I am experiencing exactly the same symptoms as described here
> http://thread.gmane.org/gmane.linux.kernel/1483297. But I run a kernel where
> that bug is fixed. And my problem happens in a VM, so it's possible that there
> are timing issues which are very unlikely on real hardware.

Can you provide a full dmesg please?

Thanks,

tglx



\
 
 \ /
  Last update: 2015-06-23 12:41    [W:0.046 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site