|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
RE: [Xen-devel] [RFC] Physical hot-add cpus and TSC
 
| 
To:  | 
"Dong, Eddie" <eddie.dong@xxxxxxxxx>, "Jiang, Yunhong"	<yunhong.jiang@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>,	"Xen-Devel (xen-devel@xxxxxxxxxxxxxxxxxxx)"	<xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx> | 
 
| 
Subject:  | 
RE: [Xen-devel] [RFC] Physical hot-add cpus and TSC | 
 
| 
From:  | 
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> | 
 
| 
Date:  | 
Thu, 10 Jun 2010 06:15:12 -0700 (PDT) | 
 
| 
Cc:  | 
 | 
 
| 
Delivery-date:  | 
Thu, 10 Jun 2010 06:18:17 -0700 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxxx | 
 
| 
In-reply-to:  | 
<1A42CE6F5F474C41B63392A5F80372B21F26E619@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> | 
 
| 
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:  | 
<789F9655DD1B8F43B48D77C5D30659731E78D370@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>	<C823EF64.1603B%keir.fraser@xxxxxxxxxxxxx>	<789F9655DD1B8F43B48D77C5D30659731E78D500@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>	<3c99c55d-68ce-4150-b895-72fda1ff3b89@default>	<789F9655DD1B8F43B48D77C5D30659731E78D89D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx	1A42CE6F5F474C41B63392A5F80372B21F26E619@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
 
 
> From: Dong, Eddie [mailto:eddie.dong@xxxxxxxxx]
> 
> > Below is test result:
> > a) With the patch
> > Before hotadd:
> > (XEN) TSC marked as reliable, warp = 0 (count=3)
> > (XEN) No domains have emulated TSC
> > (XEN) TSC marked as reliable, warp = 0 (count=4)
> > (XEN) No domains have emulated TSC
> > (XEN) TSC marked as reliable, warp = 0 (count=5)
> > (XEN) No domains have emulated TSC
> > (XEN) TSC marked as reliable, warp = 0 (count=6)
> > (XEN) No domains have emulated TSC
> >
> > After add
> > (XEN) TSC marked as reliable, warp = 1669912421214 (count=15)
> > (XEN) No domains have emulated TSC
> > (XEN) TSC marked as reliable, warp = 1669912421214 (count=16)
> > (XEN) No domains have emulated TSC
> 
> If the warp is fixed, at least for HVM, this can be solved by adjusting
> the TSC_OFFSET with the additional warp to make guest see warp=0 for
> TSC invariant case. Anything missed?
Hi Eddie --
Two things:
1) The TSC_OFFSET doesn't work for PV domains.
2) For HVM, it is very difficult to choose a precise TSC_OFFSET so
   that it passes a warp test.  If it doesn't pass a warp test,
   upstream kernels will stop using tsc as a clocksource resulting
   in a big performance loss... and some applications that use TSC
   and are not TSC resilient that may have been working fine
   for weeks may suddenly break due to an event (adding a physical
   CPU to Xen) that neither the app nor its (guest) OS is able
   to detect.
Dan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
 | 
    | 
  
  
    |   | 
    |