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/
Home Products Support Community News


RE: [Xen-devel] tsc_mode == 1 and hvm guests

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] tsc_mode == 1 and hvm guests
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 10 May 2010 17:36:48 +0100
Cc: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 10 May 2010 09:35:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bc6cb662-95fd-4fc6-abec-5b85e235865f@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>
References: <alpine.DEB.2.00.1005101341270.11380@kaball-desktop> <C80DBDC5.13CF6%keir.fraser@xxxxxxxxxxxxx> <509b3e9e-f5b2-46eb-b55e-cfea9091bc49@default> <alpine.DEB.2.00.1005101553350.11380@kaball-desktop> <c239fd37-f77b-4a17-b9c9-3833191e278c@default alpine.DEB.2.00.1005101612140.11380@kaball-desktop> <bc6cb662-95fd-4fc6-abec-5b85e235865f@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Mon, 10 May 2010, Dan Magenheimer wrote:
> > However I can tell you that without the patch when vtsc == 1
> > hvm_gtsc_need_scale returns 0 therefore scaling is never done.
> > For this reason I cannot see how the tsc frequency would remain the
> > same when vtsc == 1 and the underling hardware has a different tsc
> > rate.
> > The offset would be OK though.
> I think when vtsc==1 (e.g. tsc_mode==1), no scaling is
> done on HVM as the underlying machine is presented
> to be a 1GHz machine (regardless of the true TSC rate
> or whether migration had occurred or not).  PV also
> presented only a 1GHz clock for awhile and I changed
> it (with input from Jeremy as I recall) so that it
> would be less confusing to end users who might be
> confused by seeing Linux boot output claiming the
> underlying machine "is only running at 1GHz!!".
> There's a large number of different combinations to be
> tested (and possibly broken) here.  I'd prefer to see
> "I tested this feature on 4.0.0 and it doesn't work" before
> putting a patch into the stable stream.  For xen-unstable
> I have no problem with the patch of course.

I agree on this.
Since you definitely have the right infrastructure to test this, maybe it
is better to hold on until you can spare some time to do some more tests
on 4.0 with the patch applied.

At the moment I can only report "I tested pvlock in an HVM guest on
4.0.0 and it doesn't work".

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>