Jan Beulich writes ("[PATCH 3/5] libxencall: introduce variant of xencall2()
returning long"):
> Some hypercalls, memory-op in particular, can return values requiring
> more than 31 bits to represent. Hence the underlying layers need to make
> sure they won't truncate such values.
Thanks for this.
All 5 patches:
Acked-by: Ian Jackson <i...@xenproject.org>
Nit:
> While adding the new function to the map file, I noticed the stray
> xencall6 there. I'm taking the liberty to remove it at this occasion. If
> such a function would ever appear, it shouldn't lane in version 1.0.
^^^^
Typo for "land", I think.
Ian.
