summaryrefslogtreecommitdiff
path: root/lib/atomic64.c
diff options
context:
space:
mode:
authorValentin Schneider <valentin.schneider@arm.com>2020-11-09 09:41:17 +0000
committerMarc Zyngier <maz@kernel.org>2020-12-11 14:47:49 +0000
commit6abbd6988971aaa607b026eaa0ffd2301352f2ea (patch)
treef21a5a40fbadfc2c6f43ad2894af1075d8b76108 /lib/atomic64.c
parent550c1424acf0123ba0c17e22dfcac92d152b2f0e (diff)
irqchip/gic, gic-v3: Make SGIs use handle_percpu_devid_irq()
handle_percpu_devid_fasteoi_ipi() states: * The biggest difference with the IRQ version is that the interrupt is * EOIed early, as the IPI could result in a context switch, and we need to * make sure the IPI can fire again All that can actually happen scheduler-wise within the handling of an IPI is the raising of TIF_NEED_RESCHED (and / or folding thereof into preempt_count); see scheduler_ipi() or sched_ttwu_pending() for instance. Said flag / preempt_count is evaluated some time later before returning to whatever context was interrupted, and this gates a call to preempt_schedule_irq() (arm64_preempt_schedule_irq() in arm64). Per the above, SGI's do not need a different handler than PPI's, so make them use the same (handle_percpu_devid_irq). Signed-off-by: Valentin Schneider <valentin.schneider@arm.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20201109094121.29975-2-valentin.schneider@arm.com
Diffstat (limited to 'lib/atomic64.c')
0 files changed, 0 insertions, 0 deletions