+
ce->set_state_shutdown = hv_ce_shutdown;
ce->set_state_oneshot = hv_ce_set_oneshot;
ce->set_next_event = hv_ce_set_next_event;
LGTM.
Reviewed-by: Roman Kisel
--
Thank you,
Roman
On 5/16/2024 8:27 AM, Roman Kisel wrote:
On 5/15/2024 3:02 PM, Elliot Berman wrote:
On Tue, May 14, 2024 at 03:43:48PM -0700, Roman Kisel wrote:
The Virtual Trust Level platforms rely on DeviceTree, and the
arm64/hyperv code supports ACPI only. Update the logic to
support DeviceTree
_khz;
x86_platform.calibrate_cpu = hv_get_tsc_khz;
+ setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ);
}
if (ms_hyperv.priv_high & HV_ISOLATION) {
LGTM
Reviewed-by: Roman Kisel
--
Thank you,
Roman
On 6/7/2024 12:55 PM, Bjorn Helgaas wrote:
On Wed, May 15, 2024 at 01:12:38PM -0500, Bjorn Helgaas wrote:
On Wed, May 15, 2024 at 09:34:09AM -0700, Roman Kisel wrote:
On 5/15/2024 2:48 AM, Saurabh Singh Sengar wrote:
On Tue, May 14, 2024 at 03:43:53PM -0700, Roman Kisel wrote
On 5/19/2024 11:45 PM, Krzysztof Kozlowski wrote:
On 15/05/2024 19:33, Roman Kisel wrote:
static bool hyperv_initialized;
@@ -27,6 +30,29 @@ int hv_get_hypervisor_version(union
hv_hypervisor_version_info *info)
return 0;
}
+static bool hyperv_detect_fdt(void)
+{
+#ifdef
On 5/17/2024 10:14 AM, Rob Herring wrote:
On Tue, May 14, 2024 at 5:45 PM Roman Kisel wrote:
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
On 5/14/2024 5:00 PM, Easwar Hariharan wrote:
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
On 5/15/2024 12:43 AM, Wei Liu wrote:
On Fri, May 10, 2024 at 09:05:01AM -0700, rom...@linux.microsoft.com wrote:
From: Roman Kisel
This change removes dependency on ACPI when buidling the hv drivers to
allow Virtual Trust Level boot with DeviceTree.
Signed-off-by: Roman Kisel
On 5/15/2024 3:02 PM, Elliot Berman wrote:
On Tue, May 14, 2024 at 03:43:48PM -0700, Roman Kisel wrote:
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.
Could you use Call UID
On 5/15/2024 11:12 AM, Bjorn Helgaas wrote:
On Wed, May 15, 2024 at 09:34:09AM -0700, Roman Kisel wrote:
On 5/15/2024 2:48 AM, Saurabh Singh Sengar wrote:
On Tue, May 14, 2024 at 03:43:53PM -0700, Roman Kisel wrote:
The hyperv-pci driver uses ACPI for MSI IRQ domain configuration
On 5/15/2024 6:47 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Tuesday, May 14, 2024 3:44
PM
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.
That sentence seems a bit
On 5/15/2024 6:44 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Tuesday, May 14, 2024 3:44
PM
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
On 5/15/2024 6:39 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Tuesday, May 14, 2024 3:44
PM
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
On 5/15/2024 6:38 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Tuesday, May 14, 2024 3:44
PM
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
On 5/15/2024 6:37 AM, Michael Kelley wrote:
From: Roman Kisel Sent: Tuesday, May 14, 2024 3:44
PM
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
On 5/15/2024 12:45 AM, Krzysztof Kozlowski wrote:
On 15/05/2024 00:43, Roman Kisel wrote:
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
On 5/15/2024 12:47 AM, Krzysztof Kozlowski wrote:
On 15/05/2024 00:43, Roman Kisel wrote:
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
On 5/15/2024 2:48 AM, Saurabh Singh Sengar wrote:
On Tue, May 14, 2024 at 03:43:53PM -0700, Roman Kisel wrote:
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
On 5/15/2024 2:42 AM, Saurabh Singh Sengar wrote:
On Tue, May 14, 2024 at 03:43:52PM -0700, Roman Kisel wrote:
The vmbus driver uses ACPI for interrupt assignment on
In subject use the prefix "Drivers: hv: vmbus:".
It is preferred to us "VMbus/VMBus" instead of "
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
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
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
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
(C) 2023, Microsoft, Inc.
+ *
+ * Author : Roman Kisel
+ */
+
+#include
+
+void __init hv_vtl_init_platform(void)
+{
+ pr_info("Linux runs in Hyper-V Virtual Trust Level %d\n",
ms_hyperv.vtl);
+}
+
+int __init hv_vtl_early_init(void)
+{
+ return 0;
+}
+early_initcall(hv_vtl_
-by: Roman Kisel
---
arch/x86/hyperv/hv_init.c | 34 ---
arch/x86/include/asm/hyperv-tlfs.h | 7 -
drivers/hv/hv_common.c | 43 ++
include/asm-generic/hyperv-tlfs.h | 7 +
include/asm-generic/mshyperv.h | 6 +
5 files
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
]
- Decreased number of #ifdef's
- Updated the wording in the commit messages to adhere to the guidlines
- Sending to the correct set of maintainers and mail lists
Roman Kisel (6):
arm64/hyperv: Support DeviceTree
drivers/hv: Enable VTL mode for arm64
drivers/hv: arch-neutral implementation
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 platforms boot up on ARM64.
Signed-off-by: Roman Kisel
28 matches
Mail list logo
