Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1400076 > unrolled thread

[PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0

Started by"Rafael J. Wysocki" <rjw@rjwysocki.net>
First post2016-05-12 15:20 +0200
Last post2016-05-12 15:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

Contents

  [PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0 "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-05-12 15:20 +0200

#1400076 — [PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0

From"Rafael J. Wysocki" <rjw@rjwysocki.net>
Date2016-05-12 15:20 +0200
Subject[PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0
Message-ID<rxYH0-6wa-15@gated-at.bofh.it>
Hi,

As it turns out, all of the existing governors (and the upcoming schedutil one)
always return 0 from ->governor() for the event argument equal to _GOV_STOP
or _POLICY_EXIT.

The following two patches rearrange the core cpufreq code to take that into
account.

Thanks,
Rafael

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web