| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: system freeze when processor.ko is loaded during boo
|
To: |
Jan Beulich <JBeulich@xxxxxxxxxx>, Martin Wilck <mwilck@xxxxxxxx>, Haitao Shan <maillists.shan@xxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] Re: system freeze when processor.ko is loaded during boot |
|
From: |
Keir Fraser <keir@xxxxxxx> |
|
Date: |
Tue, 12 Apr 2011 14:59:46 +0100 |
|
Cc: |
"Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Yunhong Jiang <yunhong.jiang@xxxxxxxxx>, Donald D Dugger <donald.d.dugger@xxxxxxxxx>, Xin Li <xin.li@xxxxxxxxx>, Gang Wei <gang.wei@xxxxxxxxx> |
|
Delivery-date: |
Tue, 12 Apr 2011 07:01:19 -0700 |
|
Dkim-signature: |
v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:user-agent:date:subject:from:to:cc :message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=BV2xrdKkbu2wfbCQQve6uUOblI8S96Eziee4HP97TFk=; b=Ji9cx6BRc0hyBmpKhYL3NzU4E21no7DUsT5U/UwHYEFGF5C6GJIvV2D1zcG+FLqFK3 22agBFrjDn4FIqvzh4Om4CA/cm3gPjxW7vrnJmy3RDIE/oPV6Oxhktlm63IFp/KaJEy4 LefBvEQHLNiwk+JxvE9zFB1shEW/6PwJqMBLc= |
|
Domainkey-signature: |
a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=dyJe78BVyvDMVsocqhw0KU877MSLnDoZsIa7G9E49NEOySVoSjF002t+YNBo2RHzm3 ny31yVokUMIQEbNDISdP2jzLuUYjHSiIizqMFBV9jyV15TwQ83COwOhORGy9i5m5rYfv 2/ND9QuSccNigguQ/Lud8K2iFaFb58JmBH/Ck= |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<4D99A9F20200007800039CFB@xxxxxxxxxxxxxxxxxx> |
|
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: |
Acv5GeFSVXwB/+98M0ugUVgMTM3bnw== |
|
Thread-topic: |
[Xen-devel] Re: system freeze when processor.ko is loaded during boot |
|
User-agent: |
Microsoft-Entourage/12.28.0.101117 |
On 04/04/2011 10:22, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
> Haitao, while it is quite clear that with the current
> implementation we just can't use C states above C1 on CPUs
> that may halt the TSC in C2 or C3 *and* that don't allow
> writing the full TSC, this family/model based determination
> clearly isn't nice (and since it is a white list, it can't possibly be
> complete). An alternative would seem to be to probe for how
> TSC writes behave (thus at once covering eventual other
> vendors' CPUs that may have similar shortcomings). That of
> course would need to be done early, so that resetting the
> upper bits to zero wouldn't have any adverse effect. What
> do you think?
We should do early run-time test of this from the BSP then, on failure,
avoid all further potential uses of write_tsc() in an appropriate way (e.g.,
bail early in cstate_restore_tsc(), synchronize_tsc_*(), and avoid use of
time_calibration_tsc_rendezvous()).
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home