diff options
author | Fabiano Rosas <[email protected]> | 2022-01-25 18:56:55 -0300 |
---|---|---|
committer | Michael Ellerman <[email protected]> | 2022-01-31 13:43:00 +1100 |
commit | c1c8a66367a35aabbad9bd629b105b9fb49f2c1f (patch) | |
tree | 75092218759f4803b869bd1f97b799bc546bd7a9 /lib/test_fortify/write_overflow-strlcpy-src.c | |
parent | 349fbfe9b918e6dea00734f07c0fbaf4c2e2df5e (diff) |
KVM: PPC: Book3s: mmio: Deliver DSI after emulation failure
MMIO emulation can fail if the guest uses an instruction that we are
not prepared to emulate. Since these instructions can be and most
likely are valid ones, this is (slightly) closer to an access fault
than to an illegal instruction, so deliver a Data Storage interrupt
instead of a Program interrupt.
BookE ignores bad faults, so it will keep using a Program interrupt
because a DSI would cause a fault loop in the guest.
Suggested-by: Nicholas Piggin <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Reviewed-by: Nicholas Piggin <[email protected]>
Signed-off-by: Michael Ellerman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions