[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 16 Mar 2010 10:23:32 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Delivery-date: Tue, 16 Mar 2010 10:27:20 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 03/16/2010 04:07 AM, Stefano Stabellini wrote:

OK, you are right: having an explicit "set/remove tsc offset" is
the best solution.

I wonder if we should include scale in that API, since I think futureCPUs will allow that to be set too. (If its not supported, then thecall will fail if the scale is anything other than 1.)


    J

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

Follow-Ups:
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini

References:
- [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Sheng Yang
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Jeremy Fitzhardinge
- Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
  - From: Stefano Stabellini

Prev by Date: Re: [Xen-devel] [PATCH][v9 4/6] xen/hvm: Xen PV extension of HVM initialization
Next by Date: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
Previous by thread: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
Next by thread: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.