| commit | 17a6ddb6fac51c1979dd5e35588cc82c19e8e75c | |
| author | Marc-André Lureau <marcandre.lureau@redhat.com> | |
| Wed, 3 Oct 2018 11:44:54 +0000 (3 15:44 +0400) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Tue, 6 Nov 2018 20:35:05 +0000 (6 21:35 +0100) | ||
| tree | 191ced19c78ca22932d3254f5bccfe0b3d49bc78 | treesnapshot (tar.gz zip) |
| parent | 640713d8a17107120ba29c4b2527b0b06951e33a | commitdiff |
memory-mapping: skip non-volatile memory regions in GuestPhysBlockList
GuestPhysBlockList is currently used to produce dumps. Given the size
and the typical usage of NVDIMM for storage, they are not a good idea
to have in the dumps. We may want to have an extra dump option to
include them. For now, skip non-volatile regions.
The TCG memory clear function is going to use the GuestPhysBlockList
as well, and will thus skip NVDIMM for similar reasons.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20181003114454.5662-4-marcandre.lureau@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
GuestPhysBlockList is currently used to produce dumps. Given the size
and the typical usage of NVDIMM for storage, they are not a good idea
to have in the dumps. We may want to have an extra dump option to
include them. For now, skip non-volatile regions.
The TCG memory clear function is going to use the GuestPhysBlockList
as well, and will thus skip NVDIMM for similar reasons.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20181003114454.5662-4-marcandre.lureau@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| memory_mapping.c | diffblobblamehistory |