diff options
author | Stefan Hajnoczi | 2019-01-29 12:46:04 +0100 |
---|---|---|
committer | Peter Maydell | 2019-01-29 12:46:04 +0100 |
commit | 047be4ed24b3a408acccf9316d619477c06cca42 (patch) | |
tree | 494083f60d91dd1cb28a9c8ea78f0b4863fa0905 /win_dump.h | |
parent | target/arm: Don't clear supported PMU events when initializing PMCEID1 (diff) | |
download | qemu-047be4ed24b3a408acccf9316d619477c06cca42.tar.gz qemu-047be4ed24b3a408acccf9316d619477c06cca42.tar.xz qemu-047be4ed24b3a408acccf9316d619477c06cca42.zip |
memory: add memory_region_flush_rom_device()
ROM devices go via MemoryRegionOps->write() callbacks for write
operations and do not dirty/invalidate that memory. Device emulation
must be able to mark memory ranges that have been modified internally
(e.g. using memory_region_get_ram_ptr()).
Introduce the memory_region_flush_rom_device() API for this purpose.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-id: 20190123212234.32068-2-stefanha@redhat.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
[PMM: fix block comment style]
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'win_dump.h')
0 files changed, 0 insertions, 0 deletions