** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1768295
Title:
VLLDM/VLSTM trigger UsageFault in the Secure Mode
Status in QEMU:
Fi
Fix now in master as commit b1e5336a9899016c53d59 (and cc stable), so
should be in 3.0 and 2.12.1.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
Submitted this patch for review which should fix this bug:
https://patchwork.ozlabs.org/patch/907959/
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/b
I attached a ZIP file containing a set of binary images that reproduces
the problem.
Secure.elf and NonSecure.elf contain codes that run in the Secure/Non-
Secure mode, respectively. They must be loaded simultaneously by using
the generic loader:
$ qemu-system-arm -device loader,file=Secure.e
Yes, you're right -- I hadn't noticed this wrinkle of the architecture.
I'll put this on my todo list -- it should be straightforward.
Do you have a convenient test binary that I could use as a test case?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
