On 10/12/2015 11:15 PM, Viresh Kumar wrote:
On 12-10-15, 12:31, Saravana Kannan wrote:
Can we use the first CPU in the related CPUs mask? Instead of the
first CPU that the policy got created on? The policyX numbering
would be a bit more consistent that way.
Okay, checked this again. The problem is that ->init() isn't called
yet and we are very early in the initialization sequence. So, we can't
really know related_cpus yet. So I will keep it unchanged for now.
Can we move the sysfs add to the end so that by the time we add sysfs,
we'll have all the details?
-Saravana
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
