On Wed, Oct 22, 2014 at 1:06 PM, Rik van Riel <r...@redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/22/2014 02:07 AM, Mike Turquette wrote: >> arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow the >> scheduler to evaluate if cpu frequency should change and to invoke >> that change from a safe context. >> >> They are weakly defined arch functions that do nothing by default. >> A CPUfreq governor could use these functions to implement a >> frequency scaling policy based on updates to per-task statistics or >> updates to per-cpu utilization. >> >> As discussed at Linux Plumbers Conference 2014, the goal will be >> to focus on a single cpu frequency scaling policy that works for >> everyone. That may mean that the weak arch functions definitions >> can be removed entirely and a single policy implements that logic >> for all architectures. > > On virtual machines, we probably want to use both frequency and > steal time to calculate the factor.
You mean for calculating desired cpu frequency on a virtual guest? Is that something we want to do? Thanks, Mike > > - -- > All rights reversed > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJUSA5XAAoJEM553pKExN6DeRYH/jeXImjO2/WZFp82Yv6ukMxI > r8/kzrLMA+NS1XXCWYIcOiBqReEabkZZmypt21Tdnpkvi4GbZPpG0PEApSvOfqWE > w71J87cpMGV/e4uLcBDcvgHJX8RBQLO/ZqDcMm+zcSoeJ3G3NMK2YlZp3Uf8xqcB > tE2VGW7o2yEqNJL1fqYb++3upQmc10vIFqxVIJfP+TqZRyaVP+5kBqOMDTWb5qCV > qZjBKe1jDX5sLLGfY0ddAeuUH1iEJBIUMCcr027ezcqRp4YoqIrHRInHmNxEs5Az > 9PN8N0yGgqhvkcCfXG7He+tQBHECOnjyQlrM/2K8Cw11RziwDkC/yYIp3DPgjxc= > =f/8V > -----END PGP SIGNATURE----- -- 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/
