Date: Thu, 16 Aug 2007 00:51:51 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David P. Reed" <dpreed@reed.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: do get_rtc_time() correctly
Message-ID: <20070816005151.56176a04@the-village.bc.nu>
In-Reply-To: <46C35284.1080003@reed.com>
References: <46C35284.1080003@reed.com>
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street,
 Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a
 Lloegr o'r rhif cofrestru 3798903
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1116
Lines: 21

> So the proper way to read the RTC contents is to read the UIP flag, and 
> if zero, read all the RTC registers with interrupts masked completely, 
> so all reads happen in the 224 usec window.  (NMI can still be a 
> problem, but you can have NMI's set a flag that forces a retry).

SMM/SMI is more likely to be what bumps you 224usec or more.

> I'm happy to code and test a patch.   Rather than just submit a patch, I 
> thought I'd request others' comments on this, since it affects so many 
> architectures.  cc me, if you will, as I don't subscribe to LKML, just 
> check it periodically.

Go for it. The other architectures generally inherit it by inheriting
similar bridge chips or in more modern times the RTC macrocell. It should
also be possible to debug by putting in an optional sanity check
initially which checks the read made sense compared to a few more
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/