File Index
Files and directories
Sign in
FILE

Kconfig

File preview with syntax highlighting.

linux-6.19.14/drivers/hv/Kconfig KCONFIG
  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 SYSFB if EFI && !HYPERV_VTL_MODE
 13	select IRQ_MSI_LIB if X86
 14	help
 15	  Select this option to run Linux as a Hyper-V client operating
 16	  system.
 17
 18config HYPERV_VTL_MODE
 19	bool "Enable Linux to boot in VTL context"
 20	depends on (X86_64 && HAVE_STATIC_CALL) || ARM64
 21	depends on HYPERV
 22	depends on SMP
 23	default n
 24	help
 25	  Virtual Secure Mode (VSM) is a set of hypervisor capabilities and
 26	  enlightenments offered to host and guest partitions which enables
 27	  the creation and management of new security boundaries within
 28	  operating system software.
 29
 30	  VSM achieves and maintains isolation through Virtual Trust Levels
 31	  (VTLs). Virtual Trust Levels are hierarchical, with higher levels
 32	  being more privileged than lower levels. VTL0 is the least privileged
 33	  level, and currently only other level supported is VTL2.
 34
 35	  Select this option to build a Linux kernel to run at a VTL other than
 36	  the normal VTL0, which currently is only VTL2.  This option
 37	  initializes the kernel to run in VTL2, and adds the ability to boot
 38	  secondary CPUs directly into 64-bit context as required for VTLs other
 39	  than 0.  A kernel built with this option must run at VTL2, and will
 40	  not run as a normal guest.
 41
 42	  If unsure, say N
 43
 44config HYPERV_TIMER
 45	def_bool HYPERV && X86
 46
 47config HYPERV_UTILS
 48	tristate "Microsoft Hyper-V Utilities driver"
 49	depends on HYPERV_VMBUS && CONNECTOR && NLS
 50	depends on PTP_1588_CLOCK_OPTIONAL
 51	help
 52	  Select this option to enable the Hyper-V Utilities.
 53
 54config HYPERV_BALLOON
 55	tristate "Microsoft Hyper-V Balloon driver"
 56	depends on HYPERV_VMBUS
 57	select PAGE_REPORTING
 58	help
 59	  Select this option to enable Hyper-V Balloon driver.
 60
 61config HYPERV_VMBUS
 62	tristate "Microsoft Hyper-V VMBus driver"
 63	depends on HYPERV
 64	default HYPERV
 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
~/ Read-only file preview.