On Fri, Jan 31, 2014 at 03:09:49PM +0530, Preeti U Murthy wrote: > > Alternatively, can we enforce sanity on the cpuidle infrastructure to > > make the index naturally ordered? If not, please explain why :-) > > The commit id 71abbbf856a0e70 says that there are SOCs which could have > their target_residency and exit_latency values change at runtime. This > commit thus removed the ordering of the idle states according to their > target_residency/exit_latency. Adding Len and Arjan to the CC.
OK that changelog pretty much destroys the ordered index. In which case we need pretty accessors for useable numbers. It would be good to reduce the number of cachelines those touch, but I'm not at all familiar with the cpuidle state... -- 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/
