On 01-06-16, 00:50, Rafael J. Wysocki wrote:

I'm not particularly liking this due to the possible confusion that
may result from it.

I have gotten rid of most of it now in V2.

Perhaps we can require drivers implementing ->fast_switch to sort
their frequency tables to start with?

I wasn't *only* concerned about the fast-switch case, but the case of
normal governors that we use today. After all that's what everybody is
using right now.

And I feel (Maybe you as well), that we are better off using a single
optimized path for all cases. Otherwise things start getting too messy
too soon.

Or maybe make the core check
whether or not the table is sorted

Platforms are already broken for this, and so wouldn't be possible to
check for existing governors.

and in what order and handle it
accordingly?

We should really be handling a single order to avoid complications in
it :)

Let's just think about the design here for a while, OK?

Sure. Lets see how bad is V2.

-- 
viresh