On 01/02/19 03:49, Ning, Yu wrote:
Thank you both for outlining the changes we have to make in order to
support ROMD memory regions! The only question is whether we should
pass a new flag to HAX_VM_IOCTL_SET_RAM2 for ROMD, so the hypervisor
could respond differently to writes to ROM and ROMD regions. Would
that be useful at all? What would happen if HAXM asked QEMU to
emulate a write to ROM?
It's more about backwards compatibility. As far as QEMU is concerned
it's okay if all ROM reads are handled as MMIO. However, other
emulators may not expect that, so maybe you want to add another flag.
Paolo
HAXM didn't implement ROMD support at first, because the guests
we
tested could boot without it (including Chrome OS). Now that this
feature has become more popular (and we want to be able to boot
OVMF), I think it's time to get it done. I'd like to get to it after
the Lunar New Year holidays, but if anyone can finish it sooner, I'll
be happy to merge their patch into HAXM.