diff options
author | 2017-10-03 10:42:22 -0700 | |
---|---|---|
committer | 2017-11-27 08:42:03 -0800 | |
commit | 58721f5da4bcd5187566f4159a4fc88f70bf74f6 (patch) | |
tree | 2223b1e8a89ff15021cc6b925ec070668939090a /tools/perf/scripts/python/export-to-postgresql.py | |
parent | rcu: Clamp ->dynticks_nmi_nesting at eqs entry/exit (diff) | |
download | linux-dev-58721f5da4bcd5187566f4159a4fc88f70bf74f6.tar.xz linux-dev-58721f5da4bcd5187566f4159a4fc88f70bf74f6.zip |
rcu: Define rcu_irq_{enter,exit}() in terms of rcu_nmi_{enter,exit}()
RCU currently uses two different mechanisms for tracking irqs and NMIs.
This is unnecessary complexity: Given that NMIs can nest and given that
RCU's tracking handles such nesting, the NMI tracking mechanism can also
be used to track irqs. This commit therefore defines rcu_irq_enter()
in terms of rcu_nmi_enter() and rcu_irq_exit() in terms of rcu_nmi_exit().
Unfortunately, callers must still distinguish between the irq and NMI
functions because additional actions are taken when an irq interrupts
idle or nohz_full usermode execution, and these actions cannot always
be taken from NMI handlers.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions