diff options
author | Mark Rutland <mark.rutland@arm.com> | 2017-02-20 15:30:12 +0300 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2017-03-07 17:50:46 +0300 |
commit | ba4dd156eabdca93501d92a980ba27fa5f4bbd27 (patch) | |
tree | f70d911b1351cf97ed51c10e49d0523f32a6dd61 /Documentation | |
parent | f050fe7a9164945dd1c28be05bf00e8cfb082ccf (diff) | |
download | linux-ba4dd156eabdca93501d92a980ba27fa5f4bbd27.tar.xz |
arm64: KVM: Survive unknown traps from guests
Currently we BUG() if we see an ESR_EL2.EC value we don't recognise. As
configurable disables/enables are added to the architecture (controlled
by RES1/RES0 bits respectively), with associated synchronous exceptions,
it may be possible for a guest to trigger exceptions with classes that
we don't recognise.
While we can't service these exceptions in a manner useful to the guest,
we can avoid bringing down the host. Per ARM DDI 0487A.k_iss10775, page
D7-1937, EC values within the range 0x00 - 0x2c are reserved for future
use with synchronous exceptions, and EC values within the range 0x2d -
0x3f may be used for either synchronous or asynchronous exceptions.
The patch makes KVM handle any unknown EC by injecting an UNDEFINED
exception into the guest, with a corresponding (ratelimited) warning in
the host dmesg. We could later improve on this with with a new (opt-in)
exit to the host userspace.
Cc: Dave Martin <dave.martin@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions