13 Nov
2013
13 Nov
'13
5:56 p.m.
for picking the cpu to wake on there are also low level physical kind of things we'd want to take into account on the intel side.
Are these static and could they be hidden behind some cost number in a topology description? If they are dynamic, we would need arch or driver hooks to give some cost or priority number that the scheduler can use.
they're dynamic but slow moving (say, reevaluated once per second)
so we could have a static table that some driver updates async