forked from Minki/linux
xen/balloon: fix balloon initialization for PVH Dom0
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: Gabriel Bercarug <bercarug@amazon.com> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Reviewed-by: Juergen Gross <jgross@suse.com> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
This commit is contained in:
parent
cd9139220b
commit
3596924a23
@ -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;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user