From 95df505618a66c0f0006da0646dd760b1512c9a6 Mon Sep 17 00:00:00 2001
From: kato <kato@FreeBSD.org>
Date: Mon, 7 Apr 1997 10:53:14 +0000
Subject: Synchronize with sys/i386/isa/clock.c revision 1.80.

---
 sys/pc98/cbus/pcrtc.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

(limited to 'sys/pc98/cbus/pcrtc.c')

diff --git a/sys/pc98/cbus/pcrtc.c b/sys/pc98/cbus/pcrtc.c
index 699858f..c18ae1e 100644
--- a/sys/pc98/cbus/pcrtc.c
+++ b/sys/pc98/cbus/pcrtc.c
@@ -34,7 +34,7 @@
  * SUCH DAMAGE.
  *
  *	from: @(#)clock.c	7.2 (Berkeley) 5/12/91
- *	$Id: clock.c,v 1.17 1997/02/22 09:43:32 peter Exp $
+ *	$Id: clock.c,v 1.18 1997/03/05 16:19:48 kato Exp $
  */
 
 /*
@@ -405,15 +405,20 @@ release_timer2()
  *
  * The RTC chip requires that we read status register C (RTC_INTR)
  * to acknowledge an interrupt, before it will generate the next one.
+ * Under high interrupt load, rtcintr() can be indefinitely delayed and
+ * the clock can tick immediately after the read from RTC_INTR.  In this
+ * case, the mc146818A interrupt signal will not drop for long enough
+ * to register with the 8259 PIC.  If an interrupt is missed, the stat
+ * clock will halt, considerably degrading system performance.  This is
+ * why we use 'while' rather than a more straightforward 'if' below.
+ * Stat clock ticks can still be lost, causing minor loss of accuracy
+ * in the statistics, but the stat clock will no longer stop.
  */
 static void
 rtcintr(struct clockframe frame)
 {
-	u_char stat;
-	stat = rtcin(RTC_INTR);
-	if(stat & RTCIR_PERIOD) {
+	while (rtcin(RTC_INTR) & RTCIR_PERIOD)
 		statclock(&frame);
-	}
 }
 
 #include "opt_ddb.h"
-- 
cgit v1.1