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] [RFC] Physical hot-add cpus and TSC

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "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: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Thu, 27 May 2010 14:15:13 +0800
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Wed, 26 May 2010 23:16:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C8235082.15F50%keir.fraser@xxxxxxxxxxxxx>
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: <6b217ece-8fcf-430e-bb76-9883f798750d@default> <C8235082.15F50%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr9DCRUdsbAwjwNShi1j/opExZiCAADerkzABJtHKA=
Thread-topic: [Xen-devel] [RFC] Physical hot-add cpus and TSC

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
>Sent: Thursday, May 27, 2010 5:26 AM
>To: Dan Magenheimer; Xen-Devel (xen-devel@xxxxxxxxxxxxxxxxxxx); Ian Pratt
>Subject: Re: [Xen-devel] [RFC] Physical hot-add cpus and TSC
>On 26/05/2010 20:46, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
>>> It depends how physical CPU hotplug is implemented doesn't it. I expect
>>> there's sufficient firmware involved in such an operation that TSCs
>>> could
>>> get synced up before host software gets a look in. I don't think we can
>>> comment on whether or not there is an issue here without more
>>> information.

Yes, this is a issue. The TSC will not be synched by firmware when hot-added, 
at least I didn't find any spec on this, and my experiment shows the TSC value 
is very small when new CPU is brought up. We need sync it in Xen side,

Is it possible to sync the new-added CPU with the BSP when the CPU is added 
(changed from non-present to present), as Keir suggested in previous mail? I 
will have a look on the related code.


>>> Also, one reason Intel pushed the CPU hotplug logic is for RAS, and
>>> offlining CPUs that throw errors, which can clearly be supported with
>>> no concerns over TSC sync.
>> OK, then would you accept a patch that disables physical cpu-hot-add
>> (but not delete) unless enabled with a boot option, if the patch
>> includes sufficient commenting and dmesg to explain the ramifications?
>> Then in future if it turns out that TSC syncing is mostly always
>> handled by firmware (doubtful but possible), the default for the
>> boot option can be reversed.
>If the patch will be acked by the Intel authors of the cpu hotplug stuff
>then yes.
> -- Keir
>Xen-devel mailing list

Xen-devel mailing list