On Tue, Dec 23, 2014 at 8:52 AM, Ted Unangst <t...@tedunangst.com> wrote: > On Tue, Dec 23, 2014 at 12:20, Marinos Yannikos wrote: >> Hi, >> >> I believe that hw.setperf (as well as programs using it, such as apmd >> -C) change the CPU frequency of only single (arbitrary) cores, leading >> to higher temperatures than necessary for idle systems. It would be >> desirable if all cores were affected. >> (correct me if I'm wrong!) >> >> It doesn't seem to be easy to hack this into e.g. >> arch/amd64/amd64/est.c since there's no way to set a CPU affinity mask >> (only a P_CPUPEG for the scheduler, which is probably of limited use in >> this case). Can anyone who knows the kernel code well comment / suggest >> a course of action? A user-space implementation seems out of the >> question too with no user-facing methods available to set CPU affinity. >> > > No, it should affect all cores.
c.f. mp_setperf_init(), as called from the mainbus_attach() routine after attaching bios (and thus acpi) and the cpus. Philip Guenther
