[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 2b8371: target/arm: Use correct mmu_idx for e
From: |
GitHub |
Subject: |
[Qemu-commits] [qemu/qemu] 2b8371: target/arm: Use correct mmu_idx for exception-retu... |
Date: |
Tue, 10 Jul 2018 03:56:50 -0700 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: 2b83714d4ea659899069a4b94aa2dfadc847a013
https://github.com/qemu/qemu/commit/2b83714d4ea659899069a4b94aa2dfadc847a013
Author: Peter Maydell <address@hidden>
Date: 2018-07-10 (Tue, 10 Jul 2018)
Changed paths:
M target/arm/helper.c
Log Message:
-----------
target/arm: Use correct mmu_idx for exception-return unstacking
For M-profile exception returns, the mmu index to use for exception
return unstacking is supposed to be that of wherever we are returning to:
* if returning to handler mode, privileged
* if returning to thread mode, privileged or unprivileged depending on
CONTROL.nPRIV for the destination security state
We were passing the wrong thing as the 'priv' argument to
arm_v7m_mmu_idx_for_secstate_and_priv(). The effect was that guests
which programmed the MPU to behave differently for privileged and
unprivileged code could get spurious MemManage Unstack exceptions.
Reported-by: Adithya Baglody <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Reviewed-by: Richard Henderson <address@hidden>
Message-id: address@hidden
**NOTE:** This service been marked for deprecation:
https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] 2b8371: target/arm: Use correct mmu_idx for exception-retu...,
GitHub <=