Eric Saxe wrote: > I added the basic plumbing to have the the processor group framework > query the CPU Power manager about power manageable CPU groupings, and > then instantiate those groupings so that the dispatcher can implement > scheduling policies against them. > > The CPU power manager just has stubbing routines at this point...just > enough to create some power processor groups. Looking ahead, I believe > the CPU power manager should query the CPU PM platform driver (which > will in turn ask ACPI) to enumerate the groupings and power states. > > Also, the CPU power manager needs interfaces from the platform > driver to > implement the state changes for CPU resources. > > That should be enough mechanism for us to sprinkle some policy over to > get a basic functional prototype, I think. :) > > Mark, Anup, do you guys have some code we could populate into > cpu_pm.c and cpu_pm.h? >
Didn't get a chance to look at the code. Will PAD tell the platform CPU PM driver the next idle type the proccessor should go into? Or Does the next idle type still need to be obtained from the c-state framework itself? Thanks, -Aubrey
