RTC: Ratelimit "lost interrupts" message
We gets lots of these when the kernel is running on a hypervisor. Zach says "a guest kernel trying to get high frequency RTC will also be inaccurate, and inevitably will have unhidable interrupt lateness." Signed-off-by: Ben Collins <bcollins@ubuntu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
45807a1df9
commit
b2ff457b09
1 changed files with 2 additions and 1 deletions
|
@ -1159,7 +1159,8 @@ static void rtc_dropped_irq(unsigned long data)
|
|||
|
||||
spin_unlock_irq(&rtc_lock);
|
||||
|
||||
printk(KERN_WARNING "rtc: lost some interrupts at %ldHz.\n", freq);
|
||||
if (printk_ratelimit())
|
||||
printk(KERN_WARNING "rtc: lost some interrupts at %ldHz.\n", freq);
|
||||
|
||||
/* Now we have new data */
|
||||
wake_up_interruptible(&rtc_wait);
|
||||
|
|
Loading…
Reference in a new issue