diff options
| author | Igor Druzhinin | 2018-04-25 15:46:47 +0200 |
|---|---|---|
| committer | Stefano Stabellini | 2018-05-31 21:04:54 +0200 |
| commit | 04a8f72e877b9a912ffd7afa84209909577d1d96 (patch) | |
| tree | 0a413463d0fa4d5c735dcf9ae87d53823546c302 /include/hw/xen | |
| parent | Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180531-... (diff) | |
| download | qemu-04a8f72e877b9a912ffd7afa84209909577d1d96.tar.gz qemu-04a8f72e877b9a912ffd7afa84209909577d1d96.tar.xz qemu-04a8f72e877b9a912ffd7afa84209909577d1d96.zip | |
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>
Diffstat (limited to 'include/hw/xen')
0 files changed, 0 insertions, 0 deletions