Re: [PATCH v2 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly

2016-06-28 Thread Rafael J. Wysocki
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 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

Re: [PATCH v2 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly

2016-06-27 Thread Jisheng Zhang
Dear Rafael, On Mon, 27 Jun 2016 10:29:54 -0700 Srinivas Pandruvada 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 re

Re: [PATCH v2 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly

2016-06-27 Thread Srinivas Pandruvada
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

[PATCH v2 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly

2016-06-27 Thread Jisheng Zhang
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 writte