summaryrefslogtreecommitdiffstats
path: root/kernel/lockdep.c
diff options
context:
space:
mode:
authorGlauber Costa <glommer@redhat.com>2011-07-11 15:28:18 -0400
committerAvi Kivity <avi@redhat.com>2011-07-14 12:59:47 +0300
commit095c0aa83e52d6c3dd7168610746703921f570af (patch)
tree7461604a6040f1724bdf66c6f87e3abe60e2ad50 /kernel/lockdep.c
parente6e6685accfa81f509fadfc9624bc7c3862d75c4 (diff)
downloadop-kernel-dev-095c0aa83e52d6c3dd7168610746703921f570af.zip
op-kernel-dev-095c0aa83e52d6c3dd7168610746703921f570af.tar.gz
sched: adjust scheduler cpu power for stolen time
This patch makes update_rq_clock() aware of steal time. The mechanism of operation is not different from irq_time, and follows the same principles. This lives in a CONFIG option itself, and can be compiled out independently of the rest of steal time reporting. The effect of disabling it is that the scheduler will still report steal time (that cannot be disabled), but won't use this information for cpu power adjustments. Everytime update_rq_clock_task() is invoked, we query information about how much time was stolen since last call, and feed it into sched_rt_avg_update(). Although steal time reporting in account_process_tick() keeps track of the last time we read the steal clock, in prev_steal_time, this patch do it independently using another field, prev_steal_time_rq. This is because otherwise, information about time accounted in update_process_tick() would never reach us in update_rq_clock(). Signed-off-by: Glauber Costa <glommer@redhat.com> Acked-by: Rik van Riel <riel@redhat.com> Acked-by: Peter Zijlstra <peterz@infradead.org> Tested-by: Eric B Munson <emunson@mgebm.net> CC: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> CC: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'kernel/lockdep.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud