On Mon, Mar 16, 2020 at 09:47:44PM +, Igor Druzhinin wrote:
> args.preempted as meaningless here and doesn't show if the hypercall
^ is^ as it doesn't signal whether the
hypercall ...
> was preempted before. Use start_extent instead which is correct.
>
> Signe
On 17/03/2020 10:24, Jan Beulich wrote:
> On 16.03.2020 22:47, Igor Druzhinin wrote:
>> args.preempted as meaningless here and doesn't show if the hypercall
>> was preempted before. Use start_extent instead which is correct.
>
> ... as long as the hypercall was invoked in a "normal" way.
>
>> Sig
On 16.03.2020 22:47, Igor Druzhinin wrote:
> args.preempted as meaningless here and doesn't show if the hypercall
> was preempted before. Use start_extent instead which is correct.
... as long as the hypercall was invoked in a "normal" way.
> Signed-off-by: Igor Druzhinin
> ---
> This fixes ball
args.preempted as meaningless here and doesn't show if the hypercall
was preempted before. Use start_extent instead which is correct.
Signed-off-by: Igor Druzhinin
---
This fixes ballooning for 64-bit PV guests inside shim. 32-bit PV guests
require a little bit more work due to compat layer being
