Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1606438
| From | "Rafael J. Wysocki" <rafael@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change |
| Date | 2017-03-22 14:00 +0100 |
| Message-ID | <tnO1P-2wP-1@gated-at.bofh.it> (permalink) |
| References | <tnCWJ-31O-3@gated-at.bofh.it> <tnKUh-es-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Mar 22, 2017 at 10:29 AM, Peter Zijlstra <peterz@infradead.org> wrote: > On Wed, Mar 22, 2017 at 01:56:53AM +0100, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com> >> >> sugov_update_commit() calls trace_cpu_frequency() to record the >> current CPU frequency if it has not changed in the fast switch case >> to prevent utilities from getting confused (they may report that the >> CPU is idle if the frequency has not been recorded for too long, for >> example). > > That seems like buggy tools; we should then fix the tools, not the > kernel to emit more superfluous information. > >> However, the same problem may occur for a cpufreq driver that doesn't >> support fast frequency switching and implements the ->target callback >> (that is, it doesn't use frequency tables), but trace_cpu_frequency() >> is not called if frequency updates are skipped in that case. > > I'm having trouble parsing that; am I right in understanding this is the > exact same scenario where only superfluous changes are omitted? Yes, that's the same scenario basically, which is the point of the patch. :-) >> For this reason, modify sugov_update_commit() to always call >> trace_cpu_frequency() when the new frequency to be set is equal to >> the one that was set previously and reorganize the code in there to >> reduce duplication somewhat. > > So why not fix the tools? Because I can't. I just can't go and fix all of the tools binaries that people use out there and I want them to use recent kernels at the same time. But anyway, I think that the code with the patch looks better than without it regardless and having a frivolous difference there between the two cases is not useful.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] cpufreq: schedutil: Always trace frequency if it does not change "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2017-03-22 02:10 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Viresh Kumar <viresh.kumar@linaro.org> - 2017-03-22 05:20 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Peter Zijlstra <peterz@infradead.org> - 2017-03-22 10:40 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Viresh Kumar <viresh.kumar@linaro.org> - 2017-03-22 11:30 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change "Rafael J. Wysocki" <rafael@kernel.org> - 2017-03-22 14:00 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change "Rafael J. Wysocki" <rafael@kernel.org> - 2017-03-22 15:20 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Peter Zijlstra <peterz@infradead.org> - 2017-03-22 15:30 +0100
Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change "Rafael J. Wysocki" <rafael@kernel.org> - 2017-03-22 18:20 +0100
[PATCH v2] cpufreq: schedutil: Trace frequency only if it has changed "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2017-03-22 18:40 +0100
Re: [PATCH v2] cpufreq: schedutil: Trace frequency only if it has changed Viresh Kumar <viresh.kumar@linaro.org> - 2017-03-23 05:40 +0100
csiph-web