From: Ben Collins <bcollins@ubuntu.com>
Date: Mon, 16 Jul 2007 06:40:11 +0000 (-0700)
Subject: RTC: Ratelimit "lost interrupts" message
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=b2ff457b09554813a7df9e0cd30d5a169a257419;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git

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

diff --git a/drivers/char/rtc.c b/drivers/char/rtc.c
index 20380a2c4dee..22cf7aa56cc4 100644
--- a/drivers/char/rtc.c
+++ b/drivers/char/rtc.c
@@ -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);