Igor Druzhinin 04a8f72e87 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>		2018-05-31 12:04:54 -07:00
..
Makefile.objs	move xen-mapcache.c to hw/i386/xen/	2017-04-25 11:04:34 -07:00
trace-events	trace-events: fix code style: print 0x before hex numbers	2017-08-01 12:13:07 +01:00
xen-hvm.c	xen/hvm: correct reporting of modified memory under physmap during migration	2018-05-31 12:04:54 -07:00
xen-mapcache.c	xen/hvm: correct reporting of modified memory under physmap during migration	2018-05-31 12:04:54 -07:00
xen_apic.c	apic: add send_msi() to APICCommonClass	2016-10-17 15:44:49 -02:00
xen_platform.c	Merge remote-tracking branch 'origin/master' into HEAD	2018-01-11 22:03:50 +02:00
xen_pvdevice.c	xen-pvdevice: Introduce a simplistic xen-pvdevice save state	2018-05-18 11:01:20 -07:00