diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2018-07-20 15:56:47 +0100 |
---|---|---|
committer | Peter Maydell <peter.maydell@linaro.org> | 2018-08-02 13:19:35 +0100 |
commit | 2052c3917f5428ca51d8e50c245291b10d35c600 (patch) | |
tree | 7fefed4a5a5c07c639adb0ce5cfd5029f7917b12 /include/qemu/notify.h | |
parent | 7a1ef343a1808d36dc9f8cc415511a954bc6ce7e (diff) |
target/arm: Implement tailchaining for M profile corestarget-arm.for-3.1
Tailchaining is an optimization in handling of exception return
for M-profile cores: if we are about to pop the exception stack
for an exception return, but there is a pending exception which
is higher priority than the priority we are returning to, then
instead of unstacking and then immediately taking the exception
and stacking registers again, we can chain to the pending
exception without unstacking and stacking.
For v6M and v7M it is IMPDEF whether tailchaining happens for pending
exceptions; for v8M this is architecturally required. Implement it
in QEMU for all M-profile cores, since in practice v6M and v7M
hardware implementations generally do have it.
(We were already doing tailchaining for derived exceptions which
happened during exception return, like the validity checks and
stack access failures; these have always been required to be
tailchained for all versions of the architecture.)
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-id: 20180720145647.8810-5-peter.maydell@linaro.org
Diffstat (limited to 'include/qemu/notify.h')
0 files changed, 0 insertions, 0 deletions