Re: [PATCH 2/9] cpufreq: governor: Avoid atomic operations in hot paths

2016-02-15 Thread Viresh Kumar
On 15-02-16, 02:13, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Rework the handling of work items by dbs_update_util_handler() and > dbs_work_handler() so the former (which is executed in scheduler > paths) only uses atomic operations when absolutely necessary. That > is, when the pol

Re: [PATCH 2/9] cpufreq: governor: Avoid atomic operations in hot paths

2016-02-14 Thread Viresh Kumar
On 15-02-16, 02:13, Rafael J. Wysocki wrote: > static void dbs_irq_work(struct irq_work *irq_work) > @@ -357,6 +360,7 @@ static void dbs_update_util_handler(stru > { > struct cpu_dbs_info *cdbs = container_of(data, struct cpu_dbs_info, > update_util); > struct policy_dbs_info *policy

[PATCH 2/9] cpufreq: governor: Avoid atomic operations in hot paths

2016-02-14 Thread Rafael J. Wysocki
From: Rafael J. Wysocki Rework the handling of work items by dbs_update_util_handler() and dbs_work_handler() so the former (which is executed in scheduler paths) only uses atomic operations when absolutely necessary. That is, when the policy is shared and dbs_update_util_handler() has already d