Re: [PATCH v2 6/6] libxc: make xc_domain_maximum_gpfn() endianness-agnostic

2021-06-22 Thread Andrew Cooper
On 22/06/2021 16:20, Jan Beulich wrote: > libxc generally uses uint32_t to represent domain IDs. This is fine as > long as addresses of such variables aren't taken, to then pass into > hypercalls: To the hypervisor, a domain ID is a 16-bit value. Introduce > a wrapper struct to deal with the issue.

[PATCH v2 6/6] libxc: make xc_domain_maximum_gpfn() endianness-agnostic

2021-06-22 Thread Jan Beulich
libxc generally uses uint32_t to represent domain IDs. This is fine as long as addresses of such variables aren't taken, to then pass into hypercalls: To the hypervisor, a domain ID is a 16-bit value. Introduce a wrapper struct to deal with the issue. (On architectures with arguments passed in regi