|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: expose MWAIT to dom0
To: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: expose MWAIT to dom0 |
From: |
Keir Fraser <keir.xen@xxxxxxxxx> |
Date: |
Mon, 15 Aug 2011 07:54:54 +0100 |
Cc: |
"Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>, "'Keir Fraser \(keir@xxxxxxx\)'" <keir@xxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx> |
Delivery-date: |
Sun, 14 Aug 2011 23:55:55 -0700 |
Dkim-signature: |
v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=5HpoTpk0IaUmgjF1LeOK1XPM9odMwDZ+HjLx5s4G/RM=; b=xCcp9F7w213eM5UUzqh3jcJ4LvTnndzH/PU1DQbTUR2guP2QV09HDKRe59aZRvcLRN PcG5KUBQw0SjZEPgD05gETgpWh13W/rhAbuEz1tQkHwjZdRYRCwQoSS3vT9uZUtj+ZPW iFbWmJ0GTo3lQu8YRTGcqHVtQ3w2Jb80r5dI0= |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<625BA99ED14B2D499DC4E29D8138F15062D2E80C3A@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> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acxa+ymibBfDa2PpTRKdAF4mJFeEFAAHRLo3 |
Thread-topic: |
expose MWAIT to dom0 |
User-agent: |
Microsoft-Entourage/12.30.0.110427 |
On 15/08/2011 06:35, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
> Above trick is ugly and error-prone, since it always enable mwait regardless
> of
> actual CPU capability. It's unlikely to make into upstream, and also get lost
> in
> into some distro such as SLES11.
>
> Instead of enhancing current approach (e.g. add a separate channel to reveal
> mwait capability instead of using cpuid), I'm curious why we don't expose
> mwait
> in cpuid to dom0 directly. At least original comment in 17573 looks obscure,
> since EIST has nothing to do with Cx...
Well the problem is some older kernels will try to use MWAIT if they see the
feature in CPUID. Of course that doesn't work outside ring 0.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] expose MWAIT to dom0, Tian, Kevin
- [Xen-devel] Re: expose MWAIT to dom0,
Keir Fraser <=
- [Xen-devel] RE: expose MWAIT to dom0, Tian, Kevin
- [Xen-devel] Re: expose MWAIT to dom0, Keir Fraser
- [Xen-devel] RE: expose MWAIT to dom0, Tian, Kevin
- [Xen-devel] Re: expose MWAIT to dom0, Keir Fraser
- [Xen-devel] RE: expose MWAIT to dom0, Tian, Kevin
- [Xen-devel] RE: expose MWAIT to dom0, Jan Beulich
- [Xen-devel] Re: expose MWAIT to dom0, Keir Fraser
- [Xen-devel] RE: expose MWAIT to dom0, Tian, Kevin
- [Xen-devel] Re: expose MWAIT to dom0, Keir Fraser
- [Xen-devel] RE: expose MWAIT to dom0, Jan Beulich
|
|
|
|
|