xen/setup: Don't relocate p2m over existing one
authorRoss Lagerwall <ross.lagerwall@citrix.com>
Mon, 12 Dec 2016 14:35:13 +0000 (14:35 +0000)
committerJuergen Gross <jgross@suse.com>
Thu, 22 Dec 2016 09:04:02 +0000 (10:04 +0100)
commit7ecec8503af37de6be4f96b53828d640a968705f
treec6609057a9250b302a2cc0fc07c0e45ebb7ecf08
parent709613ad2b3c9eaeb2a3e24284b7c8feffc17326
xen/setup: Don't relocate p2m over existing one

When relocating the p2m, take special care not to relocate it so
that is overlaps with the current location of the p2m/initrd. This is
needed since the full extent of the current location is not marked as a
reserved region in the e820.

This was seen to happen to a dom0 with a large initial p2m and a small
reserved region in the middle of the initial p2m.

Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
arch/x86/xen/setup.c