[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170706161511.c7mf633xkez6d6sj@hirez.programming.kicks-ass.net>
Date: Thu, 6 Jul 2017 18:15:12 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Juri Lelli <juri.lelli@....com>, mingo@...hat.com,
rjw@...ysocki.net, viresh.kumar@...aro.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
tglx@...utronix.de, vincent.guittot@...aro.org,
luca.abeni@...tannapisa.it, claudio@...dence.eu.com,
tommaso.cucinotta@...tannapisa.it, bristot@...hat.com,
mathieu.poirier@...aro.org, tkjos@...roid.com, joelaf@...gle.com,
andresoportus@...gle.com, morten.rasmussen@....com,
dietmar.eggemann@....com, patrick.bellasi@....com
Subject: Re: [RFC PATCH v1 0/8] SCHED_DEADLINE freq/cpu invariance and OPP
selection
On Thu, Jul 06, 2017 at 11:57:15AM -0400, Steven Rostedt wrote:
> On Wed, 5 Jul 2017 09:58:57 +0100
> Juri Lelli <juri.lelli@....com> wrote:
>
> > Hi,
> >
> > v1 of the RFC set implementing frequency/cpu invariance and OPP selection for
>
> It would be nice if you specify what "OPP" stands for. A quick google
> search shows "Other Peoples Privates", which isn't the type of
> selection I would be looking for.
Its ARM speak for P-state. It stands for OPerating Point or something
like that. But yes, I too always play the Naughty by Nature song in my
head when I read that.
Powered by blists - more mailing lists