On 12/29/2024 9:46 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, December 27, 2024
10:32 AM
[...]
From a thread [1] with Nuno, my understanding is that the
include/hyperv/* files should *not* use #ifdef unless
strictly necessary because a structure or symbol is used in
arch
From: Roman Kisel Sent: Friday, December 27, 2024
10:32 AM
>
> There is no definition of the output structure for the
> GetVpRegisters hypercall. Hence, using the hypercall
> is not possible when the output value has some structure
> to it. Even getting a datum of a primitive type reads
> as ad-
: 26e1b813fcd02984b1cac5f3decdf4b0bb56fe02
patch link:
https://lore.kernel.org/r/20241227183155.122827-2-romank%40linux.microsoft.com
patch subject: [PATCH v4 1/5] hyperv: Define struct hv_output_get_vp_registers
config: arm64-randconfig-001-20241228
(https://download.01.org/0day-ci/archive/20241228
On 12/27/2024 10:31 AM, Roman Kisel wrote:
> There is no definition of the output structure for the
> GetVpRegisters hypercall. Hence, using the hypercall
> is not possible when the output value has some structure
> to it. Even getting a datum of a primitive type reads
> as ad-hoc without that defi
There is no definition of the output structure for the
GetVpRegisters hypercall. Hence, using the hypercall
is not possible when the output value has some structure
to it. Even getting a datum of a primitive type reads
as ad-hoc without that definition.
Define struct hv_output_get_vp_registers to
