From: Rik van Riel <riel@redhat.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.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 17:35:32 -0500 [thread overview]
Message-ID: <563936B4.4030308@redhat.com> (raw)
In-Reply-To: <56392FA5.5080205@intel.com>
On 11/03/2015 05:05 PM, Rafael J. Wysocki wrote:
> 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.
Not a problem. Done.
What change do I need to send in to ensure that the
linux-pm mailing list shows up in get_maintainer.pl
output?
$ ./scripts/get_maintainer.pl -f drivers/cpuidle/governors/menu.c
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
(commit_signer:4/7=57%,authored:1/7=14%,added_lines:2/19=11%,removed_lines:2/28=7%)
Daniel Lezcano <daniel.lezcano@linaro.org>
(commit_signer:3/7=43%,authored:1/7=14%,added_lines:1/19=5%)
Rik van Riel <riel@redhat.com>
(commit_signer:3/7=43%,authored:3/7=43%,added_lines:5/19=26%,removed_lines:3/28=11%)
Len Brown <len.brown@intel.com>
(commit_signer:1/7=14%,authored:1/7=14%,added_lines:10/19=53%,removed_lines:15/28=54%)
"Peter Zijlstra (Intel)" <peterz@infradead.org> (commit_signer:1/7=14%)
Javi Merino <javi.merino@arm.com>
(authored:1/7=14%,added_lines:1/19=5%,removed_lines:7/28=25%)
linux-kernel@vger.kernel.org (open list)
next prev parent reply other threads:[~2015-11-03 22:35 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 ` [PATCH 0/3] cpuidle: small improvements & fixes for menu governor Rafael J. Wysocki
2015-11-03 22:35 ` Rik van Riel [this message]
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=563936B4.4030308@redhat.com \
--to=riel@redhat.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=rafael.j.wysocki@intel.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