Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 301ae591 authored by Roger Pau Monne's avatar Roger Pau Monne Committed by Greg Kroah-Hartman
Browse files

xen/balloon: fix balloon initialization for PVH Dom0 



[ Upstream commit 3596924a233e45aa918c961a902170fc4916461b ]

The current balloon code tries to calculate a delta factor for the
balloon target when running in HVM mode in order to account for memory
used by the firmware.

This workaround for memory accounting doesn't work properly on a PVH
Dom0, that has a static-max value different from the target value even
at startup. Note that this is not a problem for DomUs because guests are
started with a static-max value that matches the amount of RAM in the
memory map.

Fix this by forcefully setting target_diff for Dom0, regardless of
it's mode.

Reported-by: default avatarGabriel Bercarug <bercarug@amazon.com>
Signed-off-by: default avatarRoger Pau Monné <roger.pau@citrix.com>
Reviewed-by: default avatarJuergen Gross <jgross@suse.com>
Signed-off-by: default avatarBoris Ostrovsky <boris.ostrovsky@oracle.com>
Signed-off-by: default avatarSasha Levin <alexander.levin@microsoft.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent a333f3f2

drivers/xen/xen-balloon.c

+1 −1
Original line number Diff line number Diff line
@@ -81,7 +81,7 @@ static void watch_target(struct xenbus_watch *watch, 
			static_max = new_target;

		else

			static_max >>= PAGE_SHIFT - 10;

		target_diff = xen_pv_domain() ? 0

		target_diff = (xen_pv_domain() || xen_initial_domain()) ? 0

				: static_max - balloon_stats.target_pages;

	}