diff options
author | Marc Zyngier <[email protected]> | 2016-01-06 18:29:19 +0000 |
---|---|---|
committer | Marc Zyngier <[email protected]> | 2016-01-24 21:55:57 +0000 |
commit | 8fc153cda9c9e6aed2a4a7235970dd6c6cb6e954 (patch) | |
tree | eae24b891572c95e695b3cfe397e5df575e0b7bf /tools/perf/scripts/python/check-perf-trace.py | |
parent | 92e963f50fc74041b5e9e744c330dca48e04f08d (diff) |
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 <[email protected]>
Tested-by: Shannon Zhao <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions