ARM: RES0/RES1 SCTLR fields not read-only
Bug #1679358 reported by
Yifan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Expired
|
Undecided
|
Unassigned |
Bug Description
There are fields in SCTLR that are RAO/SBOP or WI or in the case of the RR field, accessible only in secure mode. Currently it seems that qemu just propagates any write to SCTLR to the register and this screwed up in a bootloader that I am debugging.
tags: | added: arm |
summary: |
- ARM: SCTLR fields not being preserved + ARM: RES0/RES1 SCTLR fields not read-only |
Changed in qemu: | |
status: | New → Confirmed |
To post a comment you must log in.
On 3 April 2017 at 23:17, Yifan <email address hidden> wrote:
> There are fields in SCTLR that are RAO/SBOP or WI or in the case of the
> RR field, accessible only in secure mode. Currently it seems that qemu
> just propagates any write to SCTLR to the register and this screwed up
> in a bootloader that I am debugging.
Yes, we're a bit loose in QEMU on the handling of reserved bits.
Note that most of the SCTLR bits like this are RAO/SBOP or RAZ/SBZP,
so the guest should not be writing wrong values to them.
thanks
-- PMM