summaryrefslogtreecommitdiff
path: root/arch/arm
diff options
context:
space:
mode:
authorJames Morse <james.morse@arm.com>2018-01-15 22:38:58 +0300
committerCatalin Marinas <catalin.marinas@arm.com>2018-01-16 18:06:45 +0300
commitf751daa4f9d3da07e2777ea0c1ba2d58ff2c860f (patch)
tree5c725eb3448f516dac4ed8c64068ec0d35553d47 /arch/arm
parent6bf0dcfd713563bd2e13ceb53217305c28a8aa5f (diff)
downloadlinux-f751daa4f9d3da07e2777ea0c1ba2d58ff2c860f.tar.xz
arm64: Unconditionally enable IESB on exception entry/return for firmware-first
ARM v8.2 has a feature to add implicit error synchronization barriers whenever the CPU enters or returns from an exception level. Add this to the features we always enable. CPUs that don't support this feature will treat the bit as RES0. This feature causes RAS errors that are not yet visible to software to become pending SErrors. We expect to have firmware-first RAS support so synchronised RAS errors will be take immediately to EL3. Any system without firmware-first handling of errors will take the SError either immediatly after exception return, or when we unmask SError after entry.S's work. Adding IESB to the ELx flags causes it to be enabled by KVM and kexec too. Platform level RAS support may require additional firmware support. Cc: Christoffer Dall <christoffer.dall@linaro.org> Suggested-by: Will Deacon <will.deacon@arm.com> Link: https://www.spinics.net/lists/kvm-arm/msg28192.html Acked-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: James Morse <james.morse@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions