From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp104.sbc.mail.mud.yahoo.com (smtp104.sbc.mail.mud.yahoo.com [68.142.198.203]) by ozlabs.org (Postfix) with SMTP id C270367BB4 for ; Sun, 26 Nov 2006 10:22:41 +1100 (EST) From: David Brownell To: Benjamin Herrenschmidt Subject: Re: NTP time sync Date: Sat, 25 Nov 2006 15:22:18 -0800 References: <20061122203633.611acaa8@inspiron> <20061123105400.GA75714@muc.de> <1164279605.5653.51.camel@localhost.localdomain> In-Reply-To: <1164279605.5653.51.camel@localhost.localdomain> MIME-Version: 1.0 Message-Id: <200611251522.19900.david-b@pacbell.net> Content-Type: text/plain; charset="us-ascii" Cc: akpm@osdl.org, Alessandro Zummo , linuxppc-dev@ozlabs.org, lethal@linux-sh.org, Linux Kernel Mailing List , ralf@linux-mips.org, Andi Kleen , paulus@samba.org, rmk@arm.linux.org.uk, davem@davemloft.net, kkojima@rr.iij4u.or.jp List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thursday 23 November 2006 3:00 am, Benjamin Herrenschmidt wrote: > > Couldn't we have a transition period by making the kernel not rely on > interrupts ? if the NTP irq code just triggers a work queue, then all of > a sudden, all of the RTC drivers can be used and the latency is small. > That might well be a good enough solution and is very simple. Good point. Of course, one issue is that the NTP sync code all seems to be platform-specific right now ... just like the code to set the system time from an RTC at boot (except for the new RTC framework stuff) and after resume. - Dave