[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f14172b1-849f-41b6-ab06-799c8b51222b@linux.microsoft.com>
Date: Thu, 19 Dec 2024 12:18:38 -0800
From: Roman Kisel <romank@...ux.microsoft.com>
To: Easwar Hariharan <eahariha@...ux.microsoft.com>
Cc: Nuno Das Neves <nunodasneves@...ux.microsoft.com>, hpa@...or.com,
kys@...rosoft.com, bp@...en8.de, dave.hansen@...ux.intel.com,
decui@...rosoft.com, haiyangz@...rosoft.com, mingo@...hat.com,
mhklinux@...look.com, tglx@...utronix.de, tiala@...rosoft.com,
wei.liu@...nel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org, apais@...rosoft.com,
benhill@...rosoft.com, ssengar@...rosoft.com, sunilmut@...rosoft.com,
vdso@...bites.dev
Subject: Re: [PATCH 1/2] hyperv: Fix pointer type for the output of the
hypercall in get_vtl(void)
On 12/19/2024 12:04 PM, Easwar Hariharan wrote:
[snip]
>>
>>>
>>> This could be accompanied with migration of hv_get_vpreg128 in arm64/
>>> and removal of struct hv_get_registers_output, or that could be deferred
>>> to a later patch.
[snip]
>
> To clarify, I didn't mean to include implementing extended fast
> hypercalls with the XMM registers, or an implementation of
> hv_get_vpreg128() for x64 in my suggestion.
>
> Just to fix up the existing hv_get_vpreg128 in arch/arm64 to use
> hv_register_value (or its Linux-specific helper as Nuno suggested).
Oooh, I see, thanks! I'll try that, looks like that should be pretty
straightforward, and hopefully, it will :)
>
> Thanks,
> Easwar
--
Thank you,
Roman
Powered by blists - more mailing lists