From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: riel@redhat.com, linux-kernel@vger.kernel.org
Cc: arjan@linux.intel.com, khilman@ti.com, len.brown@intel.com,
daniel.lezcano@linaro.org, javi.merino@arm.com,
tuukka.tikkanen@linaro.org
Subject: Re: [PATCH 0/3] cpuidle: small improvements & fixes for menu governor
Date: Tue, 3 Nov 2015 23:05:25 +0100 [thread overview]
Message-ID: <56392FA5.5080205@intel.com> (raw)
In-Reply-To: <1446072416-13622-1-git-send-email-riel@redhat.com>
On 10/28/2015 11:46 PM, riel@redhat.com wrote:
> While working on a paravirt cpuidle driver for KVM guests, I
> noticed a number of small logic errors in the menu governor
> code.
>
> These patches should get rid of some artifacts that can break
> the logic in the menu governor under certain corner cases, and
> make idle state selection work better on CPUs with long C1 exit
> latencies.
>
> I have not seen any adverse effects with them in my (quick)
> tests. As expected, they do not seem to do much on systems with
> many power states and very low C1 exit latencies and target residencies.
>
Sorry for the trouble, but can you please resend the series with CCs to
linux-pm@vger.kernel.org? That will make it way easier to handle for me.
Thanks,
Rafael
next prev parent reply other threads:[~2015-11-03 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 22:46 [PATCH 0/3] cpuidle: small improvements & fixes for menu governor riel
2015-10-28 22:46 ` [PATCH 1/3] cpuidle,x86: increase forced cut-off for polling to 20us riel
2015-10-29 10:17 ` Daniel Lezcano
2015-10-29 11:54 ` Rik van Riel
2015-10-29 13:02 ` Daniel Lezcano
2015-10-28 22:46 ` [PATCH 2/3] cpuidle,menu: use interactivity_req to disable polling riel
2015-10-28 22:46 ` [PATCH 3/3] cpuidle,menu: smooth out measured_us calculation riel
2015-11-03 22:05 ` Rafael J. Wysocki [this message]
2015-11-03 22:35 ` [PATCH 0/3] cpuidle: small improvements & fixes for menu governor Rik van Riel
2015-11-03 23:03 ` Rafael J. Wysocki
2015-11-04 6:56 ` Joe Perches
2015-11-04 14:02 ` Rafael J. Wysocki
2015-11-04 15:56 ` Joe Perches
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=56392FA5.5080205@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=arjan@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=javi.merino@arm.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tuukka.tikkanen@linaro.org \
/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