summaryrefslogtreecommitdiffstats
path: root/drivers/thermal
diff options
context:
space:
mode:
authorJulien Thierry <julien.thierry@arm.com>2019-06-11 11:38:09 +0200
committerCatalin Marinas <catalin.marinas@arm.com>2019-06-21 16:49:58 +0200
commit17ce302f3117e9518395847a3120c8a108b587b8 (patch)
treec45f4cc064924854caedfd9c0ca7a78fc0838d71 /drivers/thermal
parentarm64: irqflags: Add condition flags to inline asm clobber list (diff)
downloadlinux-17ce302f3117e9518395847a3120c8a108b587b8.tar.xz
linux-17ce302f3117e9518395847a3120c8a108b587b8.zip
arm64: Fix interrupt tracing in the presence of NMIs
In the presence of any form of instrumentation, nmi_enter() should be done before calling any traceable code and any instrumentation code. Currently, nmi_enter() is done in handle_domain_nmi(), which is much too late as instrumentation code might get called before. Move the nmi_enter/exit() calls to the arch IRQ vector handler. On arm64, it is not possible to know if the IRQ vector handler was called because of an NMI before acknowledging the interrupt. However, It is possible to know whether normal interrupts could be taken in the interrupted context (i.e. if taking an NMI in that context could introduce a potential race condition). When interrupting a context with IRQs disabled, call nmi_enter() as soon as possible. In contexts with IRQs enabled, defer this to the interrupt controller, which is in a better position to know if an interrupt taken is an NMI. Fixes: bc3c03ccb464 ("arm64: Enable the support of pseudo-NMIs") Cc: <stable@vger.kernel.org> # 5.1.x- Cc: Will Deacon <will.deacon@arm.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Jason Cooper <jason@lakedaemon.net> Cc: Mark Rutland <mark.rutland@arm.com> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Julien Thierry <julien.thierry@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'drivers/thermal')
0 files changed, 0 insertions, 0 deletions