Make the bufdev and non-bufdev messages distinct, and always print the
non-constant argument (ie, the size).
This assists diagnosis.
CC: Andrew Cooper
CC: Hans van Kranenburg
---
v2: Print sizes.
---
tools/libs/call/linux.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --
On 10/15/2018 04:32 PM, Ian Jackson wrote:
> Make the bufdev and non-bufdev messages distinct, and always print the
> non-constant argument (ie, the size).
Ok, so I was doing live migration of a domU with 8GiB ram, with Xen 4.11
and Linux 4.18 in the dom0, and it consistently failed with:
xencall
On Mon, Oct 15, 2018 at 03:32:05PM +0100, Ian Jackson wrote:
> Make the bufdev and non-bufdev messages distinct, and always print the
> non-constant argument (ie, the size).
>
> This assists diagnosis.
>
> CC: Andrew Cooper
> CC: Hans van Kranenburg
Acked-by: Wei Liu