|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] RE: expose MWAIT to dom0
To: |
Keir Fraser <keir.xen@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] RE: expose MWAIT to dom0 |
From: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx> |
Date: |
Mon, 15 Aug 2011 15:13:53 +0800 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
"Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>, "'Keir Fraser \(keir@xxxxxxx\)'" <keir@xxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx> |
Delivery-date: |
Mon, 15 Aug 2011 00:16:08 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<CA6E814E.1F339%keir.xen@xxxxxxxxx> |
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: |
<625BA99ED14B2D499DC4E29D8138F15062D2E80C3A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CA6E814E.1F339%keir.xen@xxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acxa+ymibBfDa2PpTRKdAF4mJFeEFAAHRLo3AACWc5A= |
Thread-topic: |
expose MWAIT to dom0 |
> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx]
> Sent: Monday, August 15, 2011 2:55 PM
>
> 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.
>
if those old kernels are still of interest, then possibly a boot option in Xen
would
be applausive. Or can we just allow selectively exposing MWAIT when xen
cpuidle is enabled?
Thanks
Kevin
_______________________________________________
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
- RE: [Xen-devel] RE: expose MWAIT to dom0, Tian, Kevin
|
|
|
|
|