From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [RFC] [PATCH] use "reliable" tsc properly when
	available, but verify
Date: Tue, 29 Sep 2009 18:17:34 +0100
Message-ID: <C6E7FFBE.15FF2%keir.fraser@eu.citrix.com>
References: <e67b2c53-ed7b-4805-b7f0-a15e3a1d6324@default>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <e67b2c53-ed7b-4805-b7f0-a15e3a1d6324@default>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Dan Magenheimer <dan.magenheimer@oracle.com>, "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 29/09/2009 16:51, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> This proposed patch is really only important for Phase
> II, but given all the confusion around whether tsc is
> reliable/safe/constant/nonstop on various machines,
> I think it might be good to get code into Xen --
> sooner rather than later -- that "measures" this
> so we can confirm if the promises made by processor
> and system vendors are (or are not) being delivered.
> 
> Does that make more sense?

That makes it a nice-to-have. But not nice enough to have all CPUs groove
off for 2ms every once in a while, imo.

 -- Keir