mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-16 08:44:21 +08:00
24a147bcef
When a IAR register read races with a GIC interrupt RELEASE event, GIC-CPU interface could wrongly return a valid INTID to the CPU for an interrupt that is already released(non activated) instead of 0x3ff. As a side effect, an interrupt handler could run twice, once with interrupt priority and then with idle priority. As a workaround, gic_read_iar is updated so that it will return a valid interrupt ID only if there is a change in the active priority list after the IAR read on all the affected Silicons. Since there are silicon variants where both 23154 and 38545 are applicable, workaround for erratum 23154 has been extended to address both of them. Signed-off-by: Linu Cherian <lcherian@marvell.com> Reviewed-by: Marc Zyngier <maz@kernel.org> Acked-by: Catalin Marinas <catalin.marinas@arm.com> Link: https://lore.kernel.org/r/20220307143014.22758-1-lcherian@marvell.com Signed-off-by: Will Deacon <will@kernel.org> |
||
---|---|---|
.. | ||
acpi_object_usage.rst | ||
amu.rst | ||
arm-acpi.rst | ||
asymmetric-32bit.rst | ||
booting.rst | ||
cpu-feature-registers.rst | ||
elf_hwcaps.rst | ||
features.rst | ||
hugetlbpage.rst | ||
index.rst | ||
kasan-offsets.sh | ||
legacy_instructions.rst | ||
memory-tagging-extension.rst | ||
memory.rst | ||
perf.rst | ||
pointer-authentication.rst | ||
silicon-errata.rst | ||
sve.rst | ||
tagged-address-abi.rst | ||
tagged-pointers.rst |