summaryrefslogtreecommitdiffstats
path: root/firmware/atmsar11.HEX
diff options
context:
space:
mode:
authorFrederic Weisbecker <fweisbec@gmail.com>2013-07-10 00:55:25 +0200
committerFrederic Weisbecker <fweisbec@gmail.com>2013-08-13 00:54:07 +0200
commit2e70933866ace52091a3c11a5c104c063ab0c445 (patch)
treef931632cac249a8ca504eb4b0fa9373441d9cc89 /firmware/atmsar11.HEX
parentd65ec12127a5b6c6d7f5331c78157dab98a20ff0 (diff)
downloadblackbird-op-linux-2e70933866ace52091a3c11a5c104c063ab0c445.tar.gz
blackbird-op-linux-2e70933866ace52091a3c11a5c104c063ab0c445.zip
nohz: Only enable context tracking on full dynticks CPUs
The context tracking subsystem has the ability to selectively enable the tracking on any defined subset of CPU. This means that we can define a CPU range that doesn't run the context tracking and another range that does. Now what we want in practice is to enable the tracking on full dynticks CPUs only. In order to perform this, we just need to pass our full dynticks CPU range selection from the full dynticks subsystem to the context tracking. This way we can spare the overhead of RCU user extended quiescent state and vtime maintainance on the CPUs that are outside the full dynticks range. Just keep in mind the raw context tracking itself is still necessary everywhere. Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Ingo Molnar <mingo@kernel.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Li Zhong <zhong@linux.vnet.ibm.com> Cc: Mike Galbraith <efault@gmx.de> Cc: Kevin Hilman <khilman@linaro.org>
Diffstat (limited to 'firmware/atmsar11.HEX')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud