/Linux-v5.10/Documentation/ABI/stable/ |
D | sysfs-hypervisor-xen | 1 What: /sys/hypervisor/compilation/compile_date 6 Contains the build time stamp of the Xen hypervisor 8 in the hypervisor. 10 What: /sys/hypervisor/compilation/compiled_by 15 Contains information who built the Xen hypervisor 17 in the hypervisor. 19 What: /sys/hypervisor/compilation/compiler 24 Compiler which was used to build the Xen hypervisor 26 in the hypervisor. 28 What: /sys/hypervisor/properties/capabilities [all …]
|
/Linux-v5.10/Documentation/ABI/testing/ |
D | sysfs-hypervisor-xen | 1 What: /sys/hypervisor/guest_type 12 What: /sys/hypervisor/pmu/pmu_mode 24 privileged (e.g. dom0), the hypervisor 25 "all" The guest can profile itself, the hypervisor 30 What: /sys/hypervisor/pmu/pmu_features 39 What: /sys/hypervisor/properties/buildid 44 Build id of the hypervisor, needed for hypervisor live patching. 46 in the hypervisor.
|
/Linux-v5.10/Documentation/virt/kvm/arm/ |
D | hyp-abi.rst | 8 hypervisor layer when running Linux as a hypervisor (for example 10 hypervisor when running as a guest (under Xen, KVM or any other 11 hypervisor), or any hypervisor-specific interaction when the kernel is 16 booted at HYP. It can also be used by a hypervisor other than KVM 19 On arm and arm64 (without VHE), the kernel doesn't run in hypervisor 21 hypervisor to be either installed or torn down. 28 Unless specified otherwise, any built-in hypervisor must implement 36 Set HVBAR/VBAR_EL2 to 'vectors' to enable a hypervisor. 'vectors' 47 hypervisor. 61 Any other value of r0/x0 triggers a hypervisor-specific handling,
|
D | pvtime.rst | 12 some hypervisor service calls to support a paravirtualized guest obtaining a 31 PV-time feature is supported by the hypervisor. 45 meaningfully filled by the hypervisor (see structure below). 70 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
|
/Linux-v5.10/Documentation/misc-devices/ |
D | ibmvmc.rst | 24 interface between the hypervisor and a management partition. This interface 47 application using a combination of HMC to hypervisor interfaces and 50 The set of HMC to hypervisor messages supported by the management 51 application component are passed to the hypervisor over a VMC interface, 68 for communicating between the management application and the hypervisor. It 75 defined that must take place to establish that both the hypervisor and 80 when the hypervisor detects one of the peer partitions has abnormally 86 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer, 102 from the hypervisor to partition are also reported in this queue. 119 resources available in both the management partition and the hypervisor. [all …]
|
/Linux-v5.10/arch/arm/boot/dts/ |
D | xenvm-4.2.dts | 20 /* this field is going to be adjusted by the hypervisor */ 50 /* this field is going to be adjusted by the hypervisor */ 71 hypervisor { 73 /* this field is going to be adjusted by the hypervisor */ 75 /* this field is going to be adjusted by the hypervisor */
|
/Linux-v5.10/Documentation/powerpc/ |
D | papr_hcalls.rst | 12 operating system and how it should interact with the hypervisor for 15 - **IBM PowerVM (PHYP)**: IBM's proprietary hypervisor that supports AIX, 22 On PPC64 arch a guest kernel running on top of a PAPR hypervisor is called 24 issue hypercalls to the hypervisor whenever it needs to perform an action 25 that is hypervisor priviledged [3]_ or for other services managed by the 26 hypervisor. 29 asking hypervisor to perform a privileged operation on behalf of the guest. The 30 guest issues a with necessary input operands. The hypervisor after performing 36 The ABI specification for a hcall between a pseries guest and PAPR hypervisor 43 Once control is returns back to the guest after hypervisor has serviced the [all …]
|
/Linux-v5.10/Documentation/devicetree/bindings/arm/ |
D | xen.txt | 1 * Xen hypervisor device tree bindings 3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with 21 under /hypervisor with following parameters: 43 hypervisor { 58 they differ because they are provided by the Xen hypervisor, together with a set
|
/Linux-v5.10/drivers/virt/ |
D | Kconfig | 17 tristate "Freescale hypervisor management driver" 21 The Freescale hypervisor management driver provides several services 22 to drivers and applications related to the Freescale hypervisor:
|
/Linux-v5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
D | msi-pic.txt | 37 This property may be used in virtualized environments where the hypervisor 81 The Freescale hypervisor and msi-address-64 87 In a virtualized environment, the hypervisor may need to create an IOMMU 88 mapping for MSIIR. The Freescale ePAPR hypervisor has this requirement 90 (PAMU), which is currently the only IOMMU that the hypervisor supports. 106 Therefore, the hypervisor has to create a subwindow inside the same 110 address of MSIIR. The hypervisor configures the PAMU to map that address to
|
/Linux-v5.10/Documentation/virt/kvm/ |
D | running-nested-guests.rst | 6 can be KVM-based or a different hypervisor). The straightforward 32 hypervisor", as it itself is capable of running KVM. 41 hypervisor running on bare metal, adding another layer and 43 metal, running the LPAR hypervisor), L1 (host hypervisor), L2 44 (guest hypervisor), L3 (nested guest). 60 hypervisor" (level-1 guest). This in turn allows you to create 156 then the guest hypervisor will subsequently be capable of running a 163 1. On the host hypervisor (L0), enable the ``nested`` parameter on 173 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU 177 3. Now the KVM module can be loaded in the L1 (guest hypervisor):: [all …]
|
D | msr.rst | 34 whose data will be filled in by the hypervisor. The hypervisor is only 78 whose data will be filled in by the hypervisor periodically. Only one 81 The hypervisor may update this structure at any time it sees fit until 127 coordinated between the guest and the hypervisor. Availability 224 to by the hypervisor at the time of injection. Only first bit of 'flags' 236 hypervisor at the time of APF 'page ready' event injection. The content 277 whose data will be filled in by the hypervisor periodically. Only one 280 The hypervisor may update this structure at any time it sees fit until 305 the hypervisor doesn't support this field. 318 written to by the hypervisor, typically at the time of interrupt [all …]
|
D | ppc-pv.rst | 12 instructions that needlessly return us to the hypervisor even though they 16 and transforms them into unprivileged ones with some help from the hypervisor. 25 Linux is running on KVM, a node /hypervisor exists. That node contains a 34 Inside the device tree's /hypervisor node there's a property called 73 To enable communication between the hypervisor and guest there is a new shared 127 The MSR contains bits that require hypervisor intervention and bits that do 128 not require direct hypervisor intervention because they only get interpreted 129 when entering the guest or don't have any impact on the hypervisor's behavior. 213 These are the same hypercalls that pHyp, the POWER hypervisor implements. Some of
|
D | amd-memory-encryption.rst | 11 virtual machines (VMs) under the control of a hypervisor. When enabled, 15 The hypervisor can determine the SEV support through the CPUID 52 key management interface to perform common hypervisor activities such as 85 The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform 206 The KVM_SEV_DEBUG_DECRYPT command can be used by the hypervisor to request the 226 The KVM_SEV_DEBUG_ENCRYPT command can be used by the hypervisor to request the 246 The KVM_SEV_LAUNCH_SECRET command can be used by the hypervisor to inject secret 262 __u64 trans_uaddr; /* the hypervisor memory region which contains the secret */
|
/Linux-v5.10/arch/powerpc/kvm/ |
D | Kconfig | 83 tristate "KVM for POWER7 and later using hypervisor mode in host" 91 hypervisor mode available to the host. 104 tristate "KVM support without using hypervisor mode in host" 109 without using hypervisor mode in the host, by running the 113 This is not as fast as using hypervisor mode, but works on 114 machines where hypervisor mode is not available or not usable, 120 bool "Detailed timing for hypervisor real-mode code"
|
/Linux-v5.10/Documentation/admin-guide/hw-vuln/ |
D | l1tf.rst | 104 only possible, when the hypervisor does not sanitize the content of the 174 the hypervisor flushes the L1D before entering the guest. 195 address space layout of the hypervisor. 228 host OS (hypervisor) context and the other in guest context. The amount 353 managed and sanitized by the hypervisor. Though disabling EPT has a 357 EPT can be disabled in the hypervisor via the 'kvm-intel.ept' parameter. 385 flush Leaves SMT enabled and enables the default hypervisor 394 flush,nosmt Disables SMT and enables the default hypervisor mitigation, 406 off Disables hypervisor mitigations and doesn't emit any 409 on both hypervisor and bare metal. [all …]
|
/Linux-v5.10/Documentation/networking/ |
D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with 31 net_failover enables hypervisor controlled accelerated datapath to virtio-net 34 To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY 79 net_failover also enables hypervisor controlled live migration to be supported 84 the source hypervisor.
|
/Linux-v5.10/arch/sparc/mm/ |
D | tsb.c | 129 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user() 143 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user() 162 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page() 177 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page() 273 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in setup_tsb_params() 291 if (tlb_type == hypervisor) { in setup_tsb_params() 505 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in tsb_grow()
|
/Linux-v5.10/Documentation/arm64/ |
D | perf.rst | 36 This attribute excludes the hypervisor. 39 be the hypervisor. 42 hypervisor to be any code that runs at EL2 which is predominantly used for 55 kernel or non-VHE hypervisor).
|
/Linux-v5.10/arch/sparc/kernel/ |
D | setup_64.c | 180 if (tlb_type != hypervisor) { in per_cpu_patch() 202 case hypervisor: in per_cpu_patch() 284 if (tlb_type != hypervisor) in sun4v_patch() 540 else if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap() 580 if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap() 650 if (tlb_type == hypervisor) in setup_arch()
|
D | pcr.c | 255 if (tlb_type == hypervisor) { in register_perf_hsvc() 302 if (tlb_type != hypervisor) in unregister_perf_hsvc() 346 case hypervisor: in pcr_arch_init()
|
D | smp_64.c | 110 if (tlb_type == hypervisor) in smp_callin() 365 if (tlb_type == hypervisor) { in smp_boot_one_cpu() 944 if (tlb_type == hypervisor) in smp_flush_dcache_page_impl() 985 if (tlb_type == hypervisor) in flush_dcache_page_all() 1030 if (tlb_type == hypervisor && in smp_fetch_global_pmu() 1294 if (tlb_type != hypervisor) in __cpu_up() 1309 if (tlb_type == hypervisor) { in cpu_play_dead() 1473 if (tlb_type != hypervisor) in smp_init_cpu_poke() 1507 if (tlb_type == hypervisor) { in smp_send_stop() 1670 if (tlb_type == hypervisor) in setup_per_cpu_areas()
|
/Linux-v5.10/net/vmw_vsock/ |
D | Kconfig | 10 allowing communication between Virtual Machines and hypervisor 13 You should also select one or more hypervisor-specific transports 48 hypervisor.
|
/Linux-v5.10/arch/arm/kernel/ |
D | hyp-stub.S | 115 @ Now install the hypervisor stub: 117 mcr p15, 4, r7, c12, c0, 0 @ set hypervisor vector base (HVBAR)
|
/Linux-v5.10/drivers/xen/ |
D | Kconfig | 105 information with each other and with the hypervisor. 123 bool "Create xen entries under /sys/hypervisor" 128 Create entries under /sys/hypervisor describing the Xen 129 hypervisor environment. When running native or in another 130 virtual environment, /sys/hypervisor will still be present, 278 hypervisor. 281 said information to the Xen hypervisor. Then the Xen hypervisor can 319 Exports hypervisor symbols (along with their types and addresses) via
|