From: Thomas Gleixner <tglx@linutronix.de>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@elte.hu>, Daniel Walker <dwalker@mvista.com>,
mbligh@google.com, linux-kernel@vger.kernel.org,
johnstul@us.ibm.com
Subject: Re: [RFC] Fast assurate clock readable from user space and NMI handler
Date: Tue, 27 Feb 2007 09:48:41 +0100 [thread overview]
Message-ID: <1172566121.3656.2.camel@chaos> (raw)
In-Reply-To: <20070227073815.GA25894@Krystal>
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
next prev parent reply other threads:[~2007-02-27 8:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 21:59 [PATCH 8/16] LTTng 0.6.36 for 2.6.18 : Timestamp Mathieu Desnoyers
[not found] ` <1164475747.5196.5.camel@localhost.localdomain>
[not found] ` <20061126170542.GA30771@Krystal>
[not found] ` <1164561427.16871.14.camel@localhost.localdomain>
[not found] ` <20061126231833.GA22241@Krystal>
[not found] ` <1164585589.16871.52.camel@localhost.localdomain>
2007-02-24 16:19 ` [RFC] Fast assurate clock readable from user space and NMI handler Mathieu Desnoyers
2007-02-24 18:06 ` Daniel Walker
2007-02-26 20:53 ` Mathieu Desnoyers
2007-02-26 21:27 ` Daniel Walker
2007-02-26 22:14 ` Mathieu Desnoyers
2007-02-26 23:12 ` Daniel Walker
2007-02-27 3:54 ` Mathieu Desnoyers
2007-02-27 4:22 ` Daniel Walker
2007-02-27 4:47 ` Mathieu Desnoyers
2007-02-27 6:29 ` Ingo Molnar
2007-02-27 7:38 ` Mathieu Desnoyers
2007-02-27 8:48 ` Thomas Gleixner [this message]
2007-02-27 10:18 ` Daniel Walker
2007-02-27 16:02 ` Mathieu Desnoyers
2007-02-27 17:24 ` Daniel Walker
2007-02-27 19:04 ` Mathieu Desnoyers
2007-02-27 19:40 ` john stultz
2007-02-27 20:09 ` Daniel Walker
2007-02-27 9:59 ` Daniel Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172566121.3656.2.camel@chaos \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox