xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Len Brown <lenb@kernel.org>, Stefan Bader <stefan.bader@canonical.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Re: Regression in 3.1 causes Xen to use wrong idle routine
Date: Sun, 13 Nov 2011 16:59:10 +0000	[thread overview]
Message-ID: <CAE5A7DE.24C94%keir.xen@gmail.com> (raw)
In-Reply-To: <CAJvTdK=yAek4sJFXUp=kQSmnuE=HpgefN5Q-GLWhMXo=LhJ-2A@mail.gmail.com>

On 13/11/2011 03:46, "Len Brown" <lenb@kernel.org> wrote:

>> The problem I see is that select_idle_routine() is called from
>> arch/x86/kernel/cpu/common.c and since Xen setup does not set pm_idle
>> anymore, it can cause mwait_idle or amd_e400_idle functions to be selected.
>> In testing it seem amd_e400_idle in PVM domU at least does not immediately
>> cause
>> problems, but mwait_idle just causes crashes. From the reports I have
>> this may be related to older hypervisors (3.1 and older) not clearing the
>> mwait
>> capability. But overall there seems something wrong in the interaction.
> 
> Why is Xen advertising X86_FEATURE_MWAIT and then crashing
> when the dom0 (or other guests) use what it advertises?
> 
> What versions of Xen have this bug?

Xen doesn't advertise MWAIT. Possibly Xen-pv_ops is lying to the rest of the
kernel via the cpuid pv_ops hook. This would probably be because Xen is
relying on the OSPM in dom0 kernel to parse out Cx/Px info which Xen itself
*can* use.

 -- Keir



  reply	other threads:[~2011-11-13 16:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 10:24 Regression in 3.1 causes Xen to use wrong idle routine Stefan Bader
2011-10-26 13:30 ` Konrad Rzeszutek Wilk
2011-10-26 13:36   ` Stefan Bader
2011-10-26 13:48     ` Konrad Rzeszutek Wilk
2011-10-26 13:57       ` Stefan Bader
2011-11-09 17:58         ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-11-10  8:33           ` Stefan Bader
2011-11-10 14:55             ` Konrad Rzeszutek Wilk
2011-11-10 15:35               ` Stefan Bader
2011-11-13  3:46 ` Len Brown
2011-11-13 16:59   ` Keir Fraser [this message]
2011-11-14 18:19     ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-11-14 20:11       ` Konrad Rzeszutek Wilk
2011-11-14 14:31   ` Konrad Rzeszutek Wilk
2011-11-14 18:26     ` [Xen-devel] " Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE5A7DE.24C94%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=stefan.bader@canonical.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).