diff options
| author | Richard Henderson <richard.henderson@linaro.org> | 2020-09-04 12:08:24 -0700 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2020-09-07 12:34:17 +0200 |
| commit | 88e74b6122bb40852b1c98befd47a572f0c06930 (patch) | |
| tree | ffc95474b4531f624455deba98b68409cc98fe30 /target/ppc | |
| parent | cc9962d8ea80b39118d921109fd2f8db308e1d4a (diff) | |
| download | qemu-88e74b6122bb40852b1c98befd47a572f0c06930.zip qemu-88e74b6122bb40852b1c98befd47a572f0c06930.tar.gz qemu-88e74b6122bb40852b1c98befd47a572f0c06930.tar.bz2 | |
target/microblaze: Collected fixes for env->iflags
There are several problems here that can result in soft lockup,
depending on exactly where an interrupt or exception is delivered:
Include BIMM_FLAG in IFLAGS_TB_MASK, since it needs to follow D_FLAG.
Ensure that iflags is 0 when entering an interrupt/exception handler.
Add mb_cpu_synchronize_from_tb to restore iflags from tb->flags.
The change to t_sync_flags is cosmetic, but makes the code clearer.
This fixes the reported regression in acceptance/replay_kernel.py.
Fixes: 683a247ed7a4 ("target/microblaze: Store "current" iflags in insn_start")
Tested-by: Thomas Huth <thuth@redhat.com>
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20200904190842.2282109-2-richard.henderson@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'target/ppc')
0 files changed, 0 insertions, 0 deletions