_MAX pages) and is rather a cleanup. The patch is
> supposed to be applied on top of previously sent 'Drivers: hv: hv_balloon:
> survive ballooning request with num_pages=0'.
>
> Both issues were found by Laszlo Ersek during code review.
>
> Vitaly Kuznetsov (2):
>
; 104 + 2048/8 = 360
> Right limit:
> 256 + 2048/16 = 384 (so the right value is 232)
>
> We now have to make an adjustment at 8192 boundary:
> 232 + 8192/16 = 744
> 512 + 8192/32 = 768 (so the right value is 488)
>
> Suggested-by: Laszlo Ersek
> Signed-off-by: Vital
pre- and post-patch code enter
> 'more_pages = 0' branch and finish.
>
> So this patch has two real effects:
> 1) We reply with an empty response to 'num_pages=0' request.
> 2) We try a bit harder on alloc_unit=1 allocations (and reply with an empty
>
