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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 8 Apr 2017 07:30:30 +0000 (09:30 +0200)
commit8b08aec62c247db69f5e2a813912f65a46797fc2
treeb4600a96369bb85cdd6735e6db183a170b45ada3
parent8601537724611b724920fd397cc9fdb181e92ed3
xen/setup: Don't relocate p2m over existing one

commit 7ecec8503af37de6be4f96b53828d640a968705f upstream.

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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/x86/xen/setup.c