diff options
| author | Alex Williamson <alex.williamson@redhat.com> | 2016-10-31 09:53:03 -0600 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@redhat.com> | 2016-10-31 09:53:03 -0600 |
| commit | 21e00fa55f3fdfcbb20da7c6876c91ef3609b387 (patch) | |
| tree | 3bf8840920a6a9a6a0064a4711ac0617ec15b95d /memory_mapping.c | |
| parent | 0bb1137930f51a89fb1bfeb0c46aa68af0395167 (diff) | |
| download | qemu-21e00fa55f3fdfcbb20da7c6876c91ef3609b387.tar.gz | |
memory: Replace skip_dump flag with "ram_device"
Setting skip_dump on a MemoryRegion allows us to modify one specific
code path, but the restriction we're trying to address encompasses
more than that. If we have a RAM MemoryRegion backed by a physical
device, it not only restricts our ability to dump that region, but
also affects how we should manipulate it. Here we recognize that
MemoryRegions do not change to sometimes allow dumps and other times
not, so we replace setting the skip_dump flag with a new initializer
so that we know exactly the type of region to which we're applying
this behavior.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'memory_mapping.c')
| -rw-r--r-- | memory_mapping.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/memory_mapping.c b/memory_mapping.c index e3e0d95172..6a39d71da2 100644 --- a/memory_mapping.c +++ b/memory_mapping.c @@ -206,7 +206,7 @@ static void guest_phys_blocks_region_add(MemoryListener *listener, /* we only care about RAM */ if (!memory_region_is_ram(section->mr) || - memory_region_is_skip_dump(section->mr)) { + memory_region_is_ram_device(section->mr)) { return; } |