summaryrefslogtreecommitdiffstats
path: root/kernel/sys.c
diff options
context:
space:
mode:
authorThomas Renninger <trenn@suse.de>2011-02-28 22:06:34 +0100
committerRafael J. Wysocki <rjw@sisk.pl>2011-03-15 00:43:18 +0100
commitf9b9e806ae0ede772cbb9916d9ac7354a123d044 (patch)
treec855475a3b19f829999f585054e69e35af55655d /kernel/sys.c
parent7ae496187876d264c712d7c102c45edb8eb41363 (diff)
downloadop-kernel-dev-f9b9e806ae0ede772cbb9916d9ac7354a123d044.zip
op-kernel-dev-f9b9e806ae0ede772cbb9916d9ac7354a123d044.tar.gz
PM QoS: Make pm_qos settings readable
I have a machine where entering deep C-states broke. pm_qos was a hot candidate, but I couldn't find any way to double check without the need of recompiling. While in this case it was a driver bug (ath9k): https://bugzilla.kernel.org/show_bug.cgi?id=27532 powertop or others may want to read out cpu_dma_latency restrictions which could be the cause of preventing a machine entering deeper C-states. Output with this patch: # default value of 2000 * USEC_PER_SEC (0x77359400) cat /dev/network_latency |hexdump 0000000 9400 7735 0000004 # value of 55 us which is the reason for not entering C2 cat /dev/cpu_dma_latency |hexdump 0000000 0037 0000 0000004 There is no reason to hide this info -> make pm_qos files readable. Signed-off-by: Thomas Renninger <trenn@suse.de> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'kernel/sys.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud