Re: [PATCH] cpufreq, store_scaling_governor requires policy->rwsem to be held for duration of changing governors [v2]

From: Saravana Kannan
Date: Thu Jul 31 2014 - 16:38:57 EST


On 07/31/2014 01:30 PM, Prarit Bhargava wrote:


On 07/31/2014 04:24 PM, Saravana Kannan wrote:

Prarit,

I'm not an expert on sysfs locking, but I would think the specific sysfs lock
would depend on the file/attribute group. So, can you please try to hotplug a
core in/out (to trigger the POLICY_EXIT) and then read a sysfs file exported by
the governor? scaling_governor doesn't cut it since that file is not removed on
policy exit event to governor. If it's ondemand, try reading/write it's sampling
rate file.

Thanks Saravana -- will do. I will get back to you shortly on this.


Thanks. Btw, in case you weren't already aware of it. You'll have to hoplug out all the CPUs in a cluster to trigger a POLICY_EXIT for that cluster/policy.

-Saravana

--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/