Re: Question on clock drift with NO_HZ_FULL vs NO_HZ_IDLE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Feb 23, 2014 at 01:20:53AM -0600, Joel Fernandes wrote:
> Hi,
> After reading documentation, I follow that NO_HZ_FULL turns off the
> scheduling-clock interrupt on all except the boot CPU, where as
> NO_HZ_IDLE turns it off on all idle CPUs.
> 
> I understand the period scheduling-clock interrupt is required to
> compensate for hardware oscillator drift. I believe that's why
> NO_HZ_FULL keeps it ON on atleast one CPU. That way the drift is
> compensated for.
> 
> But, with NO_HZ_IDLE, all CPUs turn off interrupt during idle. Then
> how is the drift accounted for?
> 
> CC'ing Paul as well for any guidance, thanks :)

The clock code fixes things up as needed when the first CPU returns
from idle.

							Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux