From: Jisheng Zhang <jszhang@marvell.com>
To: <rjw@rjwysocki.net>, <viresh.kumar@linaro.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: regression caused by 08f511fd41c3 ("cpufreq: Reduce cpufreq_update_util() overhead a bit")
Date: Fri, 17 Jun 2016 16:40:54 +0800 [thread overview]
Message-ID: <20160617164054.6339c5d4@xhacker> (raw)
In-Reply-To: <20160617163023.5bb374f8@xhacker>
Dear all,
On Fri, 17 Jun 2016 16:30:23 +0800 Jisheng Zhang wrote:
> Dear all,
>
> I found one regression: In an idle system, wakeups/s (reported by powertop)
> is increased a lot, e.g on a intel snb 4 core platform, the wakeup event
> number is increased from 8 wakeups/s to 24 wakeup/s. bisect points to
> this commit. I could send detailed bisect log if it's wanted.
>
more information maybe useful: after the commit, the top two wakeup source
are
Process [rcu_sched]
Timer tick_sched_timer
thanks
next prev parent reply other threads:[~2016-06-17 8:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 8:30 regression caused by 08f511fd41c3 ("cpufreq: Reduce cpufreq_update_util() overhead a bit") Jisheng Zhang
2016-06-17 8:40 ` Jisheng Zhang [this message]
2016-06-17 13:09 ` Rafael J. Wysocki
2016-06-17 13:16 ` Paul E. McKenney
2016-06-17 14:03 ` Peter Zijlstra
2016-06-17 15:32 ` regression caused by bb6ab52f2bef ("intel_pstate: Do not set utilization update hook too early") Jisheng Zhang
2016-06-17 15:40 ` Rafael J. Wysocki
2016-06-17 15:42 ` Rafael J. Wysocki
2016-06-17 15:53 ` Jisheng Zhang
2016-06-17 16:09 ` Jisheng Zhang
2016-06-25 0:14 ` Rafael J. Wysocki
2016-06-25 15:09 ` Pandruvada, Srinivas
2016-06-26 0:27 ` Doug Smythies
2016-06-27 6:08 ` Jisheng Zhang
2016-06-23 16:07 ` Doug Smythies
2016-06-25 0:03 ` Rafael J. Wysocki
2016-06-17 15:32 ` regression caused by 08f511fd41c3 ("cpufreq: Reduce cpufreq_update_util() overhead a bit") Rafael J. Wysocki
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=20160617164054.6339c5d4@xhacker \
--to=jszhang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).