From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
mike@android.com, toddpoynor@google.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kandoiruchi@google.com, Juri Lelli <juri.lelli@arm.com>,
Steve Muckle <steve.muckle@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH 0/2] cpufreq: Upstream Android's Interactive governor
Date: Thu, 30 Jun 2016 13:30:22 -0700 [thread overview]
Message-ID: <20160630203022.GN12473@ubuntu> (raw)
In-Reply-To: <CAJZ5v0hW1yYD7FhOaK5Hkj7956jtQThzqY=OmCr38q_zDCjmog@mail.gmail.com>
On 20-05-16, 13:26, Rafael J. Wysocki wrote:
> On Fri, May 20, 2016 at 8:39 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > Hi Rafael et. al.,
> >
> > We had some discussions [1] last week on the PM mailing about
> > upstreaming the cpufreq governor most widely used on Andoid Mobile
> > phones and tablets: Interactive governor. People (including Rafael)
> > mostly agreed that we better get it upstreamed and here is an attempt to
> > upstream most of it (idle notifiers aren't included in this series).
> >
> > I picked the latest code spread over 70-80 patches from [2]. The
> > unmodified code, based over mainline is pushed [4] for reference.
> >
> > I have updated the governor to align it with the current practices
> > followed with mainline governors, like using utilization hooks from the
> > scheduler and handling kobject (for governor's sysfs directory) in a
> > race free manner. And of course this included general cleanup of the
> > governor as well. This version is pushed here [3] for testing.
> >
> > The Android version of interactive governor also uses idle EXIT
> > notifiers, but that code isn't part of this series and will be sent
> > separately later. For people interested in looking at that, those are 3
> > minor patches on top of this series and are pushed here [5].
> >
> > I haven't changed the core logic of the governor intentionally, as that
> > rather requires more in-depth knowledge of the use case for which the
> > optimizations have been done. So, we should do any such thing later on
> > with new patches, so that people can find things easily.
> >
> > I also haven't tried to change the userspace interface as that may have
> > broken the userspace that already exists and uses this governor.
> >
> > This has been lightly tested on my Exynos board (dual ARM A15), where
> > the governor gets inserted/removed multiple times, the sysfs files are
> > all functional. The frequency gets changed with load, etc.
> >
> > This series is based of pm/bleeding-edge branch + few patches from
> > Rafael [6] & [7] and few minor cleanups from me [8].
>
> OK, thanks!
>
> This may take some time to review, though.
Ping !!
--
viresh
next prev parent reply other threads:[~2016-06-30 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 6:39 [PATCH 0/2] cpufreq: Upstream Android's Interactive governor Viresh Kumar
2016-05-20 6:39 ` [PATCH 1/2] cpufreq: Move gov_attr_* macros to cpufreq.h Viresh Kumar
2016-05-20 6:39 ` [PATCH 2/2] cpufreq: Add android's 'interactive' governor Viresh Kumar
2016-05-20 11:26 ` [PATCH 0/2] cpufreq: Upstream Android's Interactive governor Rafael J. Wysocki
2016-06-30 20:30 ` Viresh Kumar [this message]
2016-07-01 20:48 ` 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=20160630203022.GN12473@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=juri.lelli@arm.com \
--cc=kandoiruchi@google.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike@android.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=steve.muckle@linaro.org \
--cc=toddpoynor@google.com \
--cc=vincent.guittot@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).