By banging on get_physical_address, I was able to confirm that qemu
will properly assert an exception if the VM's MMU believes the page is
read-only.
How does env-mmuregs[] get mapped to the VM's MMU? I would normally
write this off as an OpenBIOS bug, but it seems like bad behavior for
an
While working on getting SunOS to boot under qemu, I ran into a very
odd bug, and I'm not sure whose fault it is.
Excellent, there are not too many Sparc developers!
The SunOS bootloader tries to install trap 0 by writing to the trap
table. The trap table is in the .text (read-only) section
It definitely gets blocked by something: if I leave the the trap table
in the .text section, the write silently fails. If I move the trap
table to the .data section, the write succeeds. If I move the trap
table over to .rodata, the write fails again. What are you looking at
that suggests the
I don't know about sparc, but it's normal for writes to ROM to be
ignored. However by my reading the sparc bios is loaded into RAM anyway,
so it shouldn't matter.
It definitely gets blocked by something: if I leave the the trap table
in the .text section, the write silently fails. If I
Where is the policy of silently ignoring ROM writes implemented? It
may not be the proper behavior for sparc, and I'd like to tinker with
it. I'm just not sure where the write is getting suppressed (or,
alternatively, where the exception is getting suppressed).
On 2/16/07, Paul Brook [EMAIL
