summaryrefslogtreecommitdiffstats
path: root/kernel/crash_dump.c
diff options
context:
space:
mode:
authorMarc Zyngier <marc.zyngier@arm.com>2016-01-06 18:29:19 +0000
committerMarc Zyngier <marc.zyngier@arm.com>2016-01-24 21:55:57 +0000
commit8fc153cda9c9e6aed2a4a7235970dd6c6cb6e954 (patch)
treeeae24b891572c95e695b3cfe397e5df575e0b7bf /kernel/crash_dump.c
parent92e963f50fc74041b5e9e744c330dca48e04f08d (diff)
downloadlinux-8fc153cda9c9e6aed2a4a7235970dd6c6cb6e954.tar.gz
linux-8fc153cda9c9e6aed2a4a7235970dd6c6cb6e954.tar.bz2
linux-8fc153cda9c9e6aed2a4a7235970dd6c6cb6e954.zip
arm64: KVM: Fix AArch64 guest userspace exception injection
At the moment, our fault injection is pretty limited. We always generate a SYNC exception into EL1, as if the fault was actually from EL1h, no matter how it was generated. This is obviously wrong, as EL0 can generate faults of its own (not to mention the pretty-much unused EL1t mode). This patch fixes it by implementing section D1.10.2 of the ARMv8 ARM, and in particular table D1-7 ("Vector offsets from vector table base address"), which describes which vector to use depending on the source exception level and type (synchronous, IRQ, FIQ or SError). Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org> Tested-by: Shannon Zhao <shannon.zhao@linaro.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'kernel/crash_dump.c')
0 files changed, 0 insertions, 0 deletions