a94b36ddd6
We use the rom infrastructure to write firmware and/or initial kernel blobs into guest address space. So we're basically emulating the cache off phase on very early system bootup. That phase is usually responsible for clearing the instruction cache for anything it writes into cachable memory, to ensure that after reboot we don't happen to execute stale bits from the instruction cache. So we need to invalidate the icache every time we write a rom into guest address space. We do not need to do this for every DMA since the guest expects it has to flush the icache manually in that case. This fixes random reboot issues on e5500 (booke ppc) for me. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> |
||
---|---|---|
.. | ||
user | ||
address-spaces.h | ||
cpu-all.h | ||
cpu-common.h | ||
cpu-defs.h | ||
cputlb.h | ||
def-helper.h | ||
exec-all.h | ||
gdbstub.h | ||
gen-icount.h | ||
hwaddr.h | ||
ioport.h | ||
memory-internal.h | ||
memory.h | ||
poison.h | ||
softmmu_exec.h | ||
softmmu_header.h | ||
softmmu_template.h | ||
softmmu-semi.h | ||
spinlock.h |