Date: Tue, 27 Feb 2007 07:29:14 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>, mbligh@google.com,
       linux-kernel@vger.kernel.org, johnstul@us.ibm.com,
       Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Fast assurate clock readable from user space and NMI handler
Message-ID: <20070227062913.GC1259@elte.hu>
References: <20061126231833.GA22241@Krystal> <1164585589.16871.52.camel@localhost.localdomain> <20070224161906.GA9497@Krystal> <1172340369.24216.31.camel@imap.mvista.com> <20070226205304.GA30800@Krystal> <1172525261.5517.69.camel@imap.mvista.com> <20070226221423.GA2286@Krystal> <1172531521.5517.138.camel@imap.mvista.com> <20070227035456.GA15444@Krystal> <1172550161.5517.210.camel@imap.mvista.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1172550161.5517.210.camel@imap.mvista.com>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 840
Lines: 19


* Daniel Walker <dwalker@mvista.com> wrote:

> The pit clocksource could be dropped pretty easy with my clocksource 
> update patches, which I'm still working on but you could easily drop 
> clock sources that aren't atomic like the pit .. Also the pit is 
> generally undesirable, so it's not going to be missed.

that's totally unacceptable, and i'm amazed you are even suggesting it - 
often the PIT ends up being the most reliable hardware clock in a PC. 
Btw., what's wrong with the spinlock that is protecting PIT access? It 
expresses the non-atomic property of the PIT just fine.

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