| commit | 04a8f72e877b9a912ffd7afa84209909577d1d96 | |
| author | Igor Druzhinin <igor.druzhinin@citrix.com> | |
| Wed, 25 Apr 2018 13:46:47 +0000 (25 14:46 +0100) | ||
| committer | Stefano Stabellini <sstabellini@kernel.org> | |
| Thu, 31 May 2018 19:04:54 +0000 (31 12:04 -0700) | ||
| tree | 0a413463d0fa4d5c735dcf9ae87d53823546c302 | treesnapshot (tar.gz zip) |
| parent | c181ddaa176856b3cd2dfd12bbcf25fa9c884a97 | commitdiff |
xen/hvm: correct reporting of modified memory under physmap during migration
When global_log_dirty is enabled VRAM modification tracking never
worked correctly. The address that is passed to xen_hvm_modified_memory()
is not the effective PFN but RAM block address which is not the same
for VRAM.
We need to make a translation for this address into PFN using
physmap. Since there is no way to access physmap properly inside
xen_hvm_modified_memory() let's make it a global structure.
Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
When global_log_dirty is enabled VRAM modification tracking never
worked correctly. The address that is passed to xen_hvm_modified_memory()
is not the effective PFN but RAM block address which is not the same
for VRAM.
We need to make a translation for this address into PFN using
physmap. Since there is no way to access physmap properly inside
xen_hvm_modified_memory() let's make it a global structure.
Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
| hw/i386/xen/xen-hvm.c | diffblobblamehistory | |
| hw/i386/xen/xen-mapcache.c | diffblobblamehistory | |
| include/sysemu/xen-mapcache.h | diffblobblamehistory |