diff options
author | 2012-07-03 19:05:31 +0200 | |
---|---|---|
committer | 2012-07-03 19:05:31 +0200 | |
commit | dc7fd275ae60ef8edf952aff2a62462f5d892fd4 (patch) | |
tree | 620ffab8288830c8e8dc03b24e77fe3800d03b7e /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | Linux 3.5-rc5 (diff) | |
download | wireguard-linux-dc7fd275ae60ef8edf952aff2a62462f5d892fd4.tar.xz wireguard-linux-dc7fd275ae60ef8edf952aff2a62462f5d892fd4.zip |
cpuidle: move field disable from per-driver to per-cpu
Andrew J.Schorr raises a question. When he changes the disable setting on
a single CPU, it affects all the other CPUs. Basically, currently, the
disable field is per-driver instead of per-cpu. All the C states of the
same driver are shared by all CPU in the same machine.
The patch changes the `disable' field to per-cpu, so we could set this
separately for each cpu.
Signed-off-by: ShuoX Liu <shuox.liu@intel.com>
Reported-by: Andrew J.Schorr <aschorr@telemetry-investments.com>
Reviewed-by: Yanmin Zhang <yanmin_zhang@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions