1# SPDX-License-Identifier: GPL-2.0 2 3menu "Microsoft Hyper-V guest support" 4 5config HYPERV 6 bool "Microsoft Hyper-V core hypervisor support" 7 depends on (X86 && X86_LOCAL_APIC && HYPERVISOR_GUEST) \ 8 || (ARM64 && !CPU_BIG_ENDIAN) 9 select PARAVIRT 10 select X86_HV_CALLBACK_VECTOR if X86 11 select OF_EARLY_FLATTREE if OF 12 select IRQ_MSI_LIB if X86 13 help 14 Select this option to run Linux as a Hyper-V client operating 15 system. 16 17config HYPERV_VTL_MODE 18 bool "Enable Linux to boot in VTL context" 19 depends on (X86_64 && HAVE_STATIC_CALL) || ARM64 20 depends on HYPERV 21 depends on SMP 22 default n 23 help 24 Virtual Secure Mode (VSM) is a set of hypervisor capabilities and 25 enlightenments offered to host and guest partitions which enables 26 the creation and management of new security boundaries within 27 operating system software. 28 29 VSM achieves and maintains isolation through Virtual Trust Levels 30 (VTLs). Virtual Trust Levels are hierarchical, with higher levels 31 being more privileged than lower levels. VTL0 is the least privileged 32 level, and currently only other level supported is VTL2. 33 34 Select this option to build a Linux kernel to run at a VTL other than 35 the normal VTL0, which currently is only VTL2. This option 36 initializes the kernel to run in VTL2, and adds the ability to boot 37 secondary CPUs directly into 64-bit context as required for VTLs other 38 than 0. A kernel built with this option must run at VTL2, and will 39 not run as a normal guest. 40 41 If unsure, say N 42 43config HYPERV_TIMER 44 def_bool HYPERV && X86 45 46config HYPERV_UTILS 47 tristate "Microsoft Hyper-V Utilities driver" 48 depends on HYPERV_VMBUS && CONNECTOR && NLS 49 depends on PTP_1588_CLOCK_OPTIONAL 50 help 51 Select this option to enable the Hyper-V Utilities. 52 53config HYPERV_BALLOON 54 tristate "Microsoft Hyper-V Balloon driver" 55 depends on HYPERV_VMBUS 56 select PAGE_REPORTING 57 help 58 Select this option to enable Hyper-V Balloon driver. 59 60config HYPERV_VMBUS 61 tristate "Microsoft Hyper-V VMBus driver" 62 depends on HYPERV 63 default HYPERV 64 select SYSFB if EFI && !HYPERV_VTL_MODE 65 help 66 Select this option to enable Hyper-V Vmbus driver. 67 68config MSHV_ROOT 69 tristate "Microsoft Hyper-V root partition support" 70 depends on HYPERV && (X86_64 || ARM64) 71 depends on !HYPERV_VTL_MODE 72 # The hypervisor interface operates on 4k pages. Enforcing it here 73 # simplifies many assumptions in the root partition code. 74 # e.g. When withdrawing memory, the hypervisor gives back 4k pages in 75 # no particular order, making it impossible to reassemble larger pages 76 depends on PAGE_SIZE_4KB 77 select EVENTFD 78 select VIRT_XFER_TO_GUEST_WORK 79 select HMM_MIRROR 80 select MMU_NOTIFIER 81 default n 82 help 83 Select this option to enable support for booting and running as root 84 partition on Microsoft Hyper-V. 85 86 If unsure, say N. 87 88config MSHV_VTL 89 tristate "Microsoft Hyper-V VTL driver" 90 depends on X86_64 && HYPERV_VTL_MODE 91 depends on HYPERV_VMBUS 92 # Mapping VTL0 memory to a userspace process in VTL2 is supported in OpenHCL. 93 # VTL2 for OpenHCL makes use of Huge Pages to improve performance on VMs, 94 # specially with large memory requirements. 95 depends on TRANSPARENT_HUGEPAGE 96 # MTRRs are controlled by VTL0, and are not specific to individual VTLs. 97 # Therefore, do not attempt to access or modify MTRRs here. 98 depends on !MTRR 99 select CPUMASK_OFFSTACK 100 select VIRT_XFER_TO_GUEST_WORK 101 default n 102 help 103 Select this option to enable Hyper-V VTL driver support. 104 This driver provides interfaces for Virtual Machine Manager (VMM) running in VTL2 105 userspace to create VTLs and partitions, setup and manage VTL0 memory and 106 allow userspace to make direct hypercalls. This also allows to map VTL0's address 107 space to a usermode process in VTL2 and supports getting new VMBus messages and channel 108 events in VTL2. 109 110 If unsure, say N. 111 112endmenu 113