WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] mask cpuid TSC invariant bit for various circums

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] mask cpuid TSC invariant bit for various circumstances (Take 2)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 06 Nov 2009 07:18:09 +0000
Cc:
Delivery-date: Thu, 05 Nov 2009 23:18:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4c6eda4b-48c0-4a29-9800-c66a18a0f89f@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpeZHPcRq2yMsrISR2YFtig5R3aCAATNbms
Thread-topic: [Xen-devel] [PATCH] mask cpuid TSC invariant bit for various circumstances (Take 2)
User-agent: Microsoft-Entourage/12.20.0.090605
On 05/11/2009 21:50, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> Mask cpuid TSC invariant bit for some circumstances
> and expose it for others.  On upstream Linux kernels,
> non-zero Invariant TSC bit permanently selects TSC
> as the clocksource (currently on Intel only).  When
> these kernels run on Xen, when migration is possible
> and TSC is unemulated, this can cause much weirdness.
> But exposing non-zero Invariant TSC has performance
> advantages so we want to expose it when it is safe.
> (Note leaving it exposed/unexposed for dom0 is not an
> issue.)

I think I pushed you into changing this in a way I like even less. :-) I can
live with your original patch, so I'll check that in after all.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel