Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks

From	Viresh Kumar <viresh.kumar@linaro.org>
Newsgroups	linux.kernel
Subject	Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks
Date	2017-07-31 06:00 +0200
Message-ID	<u9a25-15b-5@gated-at.bofh.it> (permalink)
References	(3 earlier) <u7BJ8-5vg-19@gated-at.bofh.it> <u7HOx-QN-1@gated-at.bofh.it> <u7X6V-21e-5@gated-at.bofh.it> <u86Df-8nH-1@gated-at.bofh.it> <u8kGe-C9-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 28-07-17, 14:05, Saravana Kannan wrote:
> 1. I'm not saying that. I'm saying assuming CPUs can change the freq only on
> behalf of all the CPUs in the same policy is wrong. Again, the scheduler or
> governor shouldn't even be making any of that assumption. That's a CPUfreq
> driver problem.
> 
> 2. No, that is not the basis of the entire cpufreq core design. None of the
> existing CPUfreq code has any assumptions that only CPUs in a policy can
> change their frequency. It doesn't break in any way in system where any CPU
> can change any other CPU's frequency -- all Qualcomm chips are like that.
> It's only the recent scheduler notifier changes that are adding this
> additional limitation and breaking stuff for systems where any CPU can
> change any other CPU's frequency.

Can you please have a look at V5 and see f the solution proposed there would be
fine ?

-- 
viresh

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Peter Zijlstra <peterz@infradead.org> - 2017-07-21 15:10 +0200
  Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-24 13:10 +0200
    Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Peter Zijlstra <peterz@infradead.org> - 2017-07-24 15:50 +0200
      Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-26 08:30 +0200
        Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Peter Zijlstra <peterz@infradead.org> - 2017-07-26 10:20 +0200
        Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2017-07-26 19:40 +0200
  Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Saravana Kannan <skannan@codeaurora.org> - 2017-07-26 23:10 +0200
    Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-27 05:40 +0200
      Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Saravana Kannan <skannan@codeaurora.org> - 2017-07-27 22:00 +0200
        Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks "Joel Fernandes (Google)" <joel.opensrc@gmail.com> - 2017-07-28 06:40 +0200
        Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-28 08:10 +0200
          Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Saravana Kannan <skannan@codeaurora.org> - 2017-07-28 23:10 +0200
            Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq  callbacks Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-31 06:00 +0200

csiph-web