[PATCH v2 0/6] arm64/hyperv: Support Virtual Trust Level Boot

2024-05-14 Thread Roman Kisel
This patch set enables the Hyper-V code to boot on ARM64 inside a Virtual Trust Level. These levels are a part of the Virtual Secure Mode documented in the Top-Level Functional Specification available at https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/vsm [V2] - Decrea

[PATCH v2 2/6] drivers/hv: Enable VTL mode for arm64

2024-05-14 Thread Roman Kisel
Kconfig dependencies for arm64 guests on Hyper-V require that be ACPI enabled, and limit VTL mode to x86/x64. To enable VTL mode on arm64 as well, update the dependencies. Since VTL mode requires DeviceTree instead of ACPI, don’t require arm64 guests on Hyper-V to have ACPI. Signed-off-by: Roman K

[PATCH v2 3/6] drivers/hv: arch-neutral implementation of get_vtl()

2024-05-14 Thread Roman Kisel
To run in the VTL mode, Hyper-V drivers have to know what VTL the system boots in, and the arm64/hyperv code does not have the means to compute that. Refactor the code to hoist the function that detects VTL, make it arch-neutral to be able to employ it to get the VTL on arm64. Signed-off-by: Roma

[PATCH v2 4/6] arm64/hyperv: Boot in a Virtual Trust Level

2024-05-14 Thread Roman Kisel
To run in the VTL mode, Hyper-V drivers have to know what VTL the system boots in, and the arm64/hyperv code does not update the variable that stores the value. Update the variable to enable the Hyper-V drivers to boot in the VTL mode and print the VTL the code runs in. Signed-off-by: Roman Kisel

[PATCH v2 5/6] drivers/hv/vmbus: Get the irq number from DeviceTree

2024-05-14 Thread Roman Kisel
The vmbus driver uses ACPI for interrupt assignment on arm64 hence it won't function in the VTL mode where only DeviceTree can be used. Update the vmbus driver to discover interrupt configuration via DeviceTree. Signed-off-by: Roman Kisel --- drivers/hv/vmbus_drv.c | 37

[PATCH v2 1/6] arm64/hyperv: Support DeviceTree

2024-05-14 Thread Roman Kisel
The Virtual Trust Level platforms rely on DeviceTree, and the arm64/hyperv code supports ACPI only. Update the logic to support DeviceTree on boot as well as ACPI. Signed-off-by: Roman Kisel --- arch/arm64/hyperv/mshyperv.c | 34 +- 1 file changed, 29 insertions(+

[PATCH v2 6/6] drivers/pci/hyperv/arm64: vPCI MSI IRQ domain from DT

2024-05-14 Thread Roman Kisel
The hyperv-pci driver uses ACPI for MSI IRQ domain configuration on arm64 thereby it won't be able to do that in the VTL mode where only DeviceTree can be used. Update the hyperv-pci driver to discover interrupt configuration via DeviceTree. Signed-off-by: Roman Kisel --- drivers/pci/controller

Re: [PATCH 1/6] arm64/hyperv: Support DeviceTree

2024-05-14 Thread Easwar Hariharan
On 5/10/2024 10:42 AM, Roman Kisel wrote: > > > On 5/10/2024 10:04 AM, Easwar Hariharan wrote: >> On 5/10/2024 9:05 AM, rom...@linux.microsoft.com wrote: >>> From: Roman Kisel >>> >>> Update the driver to support DeviceTree boot as well along with ACPI. >>> This enables the Virtual Trust Level p

Re: [PATCH 1/6] arm64/hyperv: Support DeviceTree

2024-05-14 Thread Roman Kisel
On 5/14/2024 3:46 PM, Easwar Hariharan wrote: On 5/10/2024 10:42 AM, Roman Kisel wrote: On 5/10/2024 10:04 AM, Easwar Hariharan wrote: On 5/10/2024 9:05 AM, rom...@linux.microsoft.com wrote: From: Roman Kisel Update the driver to support DeviceTree boot as well along with ACPI. This ena

Re: [PATCH 1/6] arm64/hyperv: Support DeviceTree

2024-05-14 Thread Easwar Hariharan
On 5/14/2024 4:17 PM, Roman Kisel wrote: > > > On 5/14/2024 3:46 PM, Easwar Hariharan wrote: >> On 5/10/2024 10:42 AM, Roman Kisel wrote: >>> >>> >>> On 5/10/2024 10:04 AM, Easwar Hariharan wrote: On 5/10/2024 9:05 AM, rom...@linux.microsoft.com wrote: > From: Roman Kisel > > Up