Messages in this thread | | | Subject | Re: [RFC] Fast assurate clock readable from user space and NMI handler | From | Thomas Gleixner <> | Date | Tue, 27 Feb 2007 09:48:41 +0100 |
| |
On Tue, 2007-02-27 at 02:38 -0500, Mathieu Desnoyers 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. > > > > I am concerned about the automatic fallback to the PIT when no other > clock source is available.
And what are you going to use then ? Just kill the box, when nothing else than PIT is there ?
tglx
- 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/
| |