[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27685849.lNYHADO2Ux@vostro.rjw.lan>
Date: Tue, 28 Jun 2016 13:43:05 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Jisheng Zhang <jszhang@...vell.com>
Cc: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
lenb@...nel.org, viresh.kumar@...aro.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly
On Tuesday, June 28, 2016 10:29:27 AM Jisheng Zhang wrote:
> Dear Rafael,
>
> On Mon, 27 Jun 2016 10:29:54 -0700
> Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com> wrote:
>
> > On Mon, 2016-06-27 at 18:07 +0800, Jisheng Zhang wrote:
> > > pid_params is written once by copy_pid_params() during
> > > initialization,
> > > and thereafter is mostly read by hot path intel_pstate_update_util().
> > > The read of pid_params gets more after commit a4675fbc4a7a ("cpufreq:
> > > intel_pstate: Replace timers with utilization update callbacks")
> > >
> > > pstate_funcs is written once by copy_cpu_funcs() during
> > > initialization,
> > > and thereafter is mostly read by hot path intel_pstate_update_util()
> > >
> > > hwp_active is written to once during initialization and thereafter is
> > > mostly read by hot path intel_pstate_update_util().
> > >
> > > The fact that they are mostly read and not written to makes them
> > > candidates for __read_mostly declarations.
> > >
> > > Signed-off-by: Jisheng Zhang <jszhang@...vell.com>
> > Acked-by: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
>
> oops, I missed Viresh's Ack in this patch, so can you please add the missing
>
> Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
I've added it already.
Thanks,
Rafael
Powered by blists - more mailing lists