From: Stefan Bader <stefan.bader@canonical.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: len.brown@intel.com,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Regression in 3.1 causes Xen to use wrong idle routine
Date: Wed, 26 Oct 2011 15:57:15 +0200 [thread overview]
Message-ID: <4EA811BB.6010005@canonical.com> (raw)
In-Reply-To: <20111026134843.GA31609@phenom.dumpdata.com>
On 26.10.2011 15:48, Konrad Rzeszutek Wilk wrote:
>>> What about using the cpuidle_disabled() functionality and adhere to that?
>>> As so:
>>>
> .. snip..
>>
>> >From reading over it, this should work. Though I would be interested to hear
>> from the linux-acpi folks. Also to double check that calling pm_idle when
>> cpuidle.off was specified really is what is intended.
>
> Oh yeah, definitly need the input from linux-acpi folks. And also to be actually
> tested :-)
I can volunteer to do the testing. But I am lazy enough to hold back a bit as
someone may tell us this is completely the wrong way to fix it. :)
next prev parent reply other threads:[~2011-10-26 13:57 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 [this message]
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 ` [Xen-devel] " Keir Fraser
2011-11-14 18:19 ` 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=4EA811BB.6010005@canonical.com \
--to=stefan.bader@canonical.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--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).