diff options
author | Paul E. McKenney <paulmck@kernel.org> | 2020-02-13 12:31:16 -0800 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2020-05-05 11:27:42 +0200 |
commit | dedd668bca69f7415fa1a126f313b5e7f5585556 (patch) | |
tree | 5a58b64c93153ce4c7f5b2e9f6cb2e4af11f53d2 /scripts/export_report.pl | |
parent | 6064b2069b75dc1f2ab043d8e9484a0d12f05f9e (diff) |
rcu: Make RCU IRQ enter/exit functions rely on in_nmi()entry-v4-part1
The rcu_nmi_enter_common() and rcu_nmi_exit_common() functions take an
"irq" parameter that indicates whether these functions are invoked from
an irq handler (irq==true) or an NMI handler (irq==false). However,
recent changes have applied notrace to a few critical functions such
that rcu_nmi_enter_common() and rcu_nmi_exit_common() many now rely
on in_nmi(). Note that in_nmi() works no differently than before,
but rather that tracing is now prohibited in code regions where in_nmi()
would incorrectly report NMI state.
Therefore remove the "irq" parameter and inlines rcu_nmi_enter_common() and
rcu_nmi_exit_common() into rcu_nmi_enter() and rcu_nmi_exit(),
respectively.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'scripts/export_report.pl')
0 files changed, 0 insertions, 0 deletions