Searched hist:"21 e00fa55f3fdfcbb20da7c6876c91ef3609b387" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/qemu/hw/vfio/ |
| H A D | spapr.c | diff 21e00fa55f3fdfcbb20da7c6876c91ef3609b387 Mon Oct 31 10:53:03 CDT 2016 Alex Williamson <alex.williamson@redhat.com> 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>
|
| H A D | common.c | diff 21e00fa55f3fdfcbb20da7c6876c91ef3609b387 Mon Oct 31 10:53:03 CDT 2016 Alex Williamson <alex.williamson@redhat.com> 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>
|
| /openbmc/qemu/include/exec/ |
| H A D | memory.h | diff 21e00fa55f3fdfcbb20da7c6876c91ef3609b387 Mon Oct 31 10:53:03 CDT 2016 Alex Williamson <alex.williamson@redhat.com> 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>
|