| /linux/Documentation/ABI/stable/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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/Documentation/virt/kvm/arm/ |
| H A 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. 71 Any other value of r0/x0 triggers a hypervisor-specific handling,
|
| H A D | pvtime.rst | 12 some hypervisor service calls to support a paravirtualized guest obtaining a 32 PV-time feature is supported by the hypervisor. 47 meaningfully filled by the hypervisor (see structure below). 72 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
|
| /linux/Documentation/misc-devices/ |
| H A 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/arch/arm/boot/dts/xen/ |
| H A 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/Documentation/virt/acrn/ |
| H A D | introduction.rst | 6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal 13 hypervisor services to the ACRN userspace. 38 ioctls to communicate with the HSM. HSM implements hypervisor services by 42 The ACRN hypervisor is open for contribution from anyone. The source repo is 43 available at https://github.com/projectacrn/acrn-hypervisor.
|
| H A D | io-request.rst | 6 An I/O request of a User VM, which is constructed by the hypervisor, is 15 communication between the hypervisor and Service VM. An I/O request is a 17 an I/O handler of the hypervisor when a trapped I/O access happens in a User 19 the GPA (Guest Physical Address) of the buffer to the hypervisor. The buffer is 81 An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and 87 a. The I/O handler of the hypervisor will fill an I/O request with PENDING 89 b. The hypervisor makes an upcall, which is a notification interrupt, to 96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor
|
| /linux/drivers/virt/ |
| H A D | Kconfig | 20 Say Y here to use the hypervisor-provided Virtual Machine Generation ID 27 tristate "Freescale hypervisor management driver" 31 The Freescale hypervisor management driver provides several services 32 to drivers and applications related to the Freescale hypervisor:
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | xen.txt | 1 * Xen hypervisor device tree bindings 3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with 23 under /hypervisor with following parameters: 45 hypervisor { 60 they differ because they are provided by the Xen hypervisor, together with a set
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 8 can be KVM-based or a different hypervisor). The straightforward 34 hypervisor", as it itself is capable of running KVM. 43 hypervisor running on bare metal, adding another layer and 45 metal, running the LPAR hypervisor), L1 (host hypervisor), L2 46 (guest hypervisor), L3 (nested guest). 62 hypervisor" (level-1 guest). This in turn allows you to create 158 then the guest hypervisor will subsequently be capable of running a 165 1. On the host hypervisor (L0), enable the ``nested`` parameter on 175 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU 179 3. Now the KVM module can be loaded in the L1 (guest hypervisor):: [all …]
|
| H A 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 223 to by the hypervisor at the time of injection. Only first bit of 'flags' 235 hypervisor at the time of APF 'page ready' event injection. The content 276 whose data will be filled in by the hypervisor periodically. Only one 279 The hypervisor may update this structure at any time it sees fit until 304 the hypervisor doesn't support this field. 317 written to by the hypervisor, typically at the time of interrupt [all …]
|
| /linux/arch/arm64/kvm/ |
| H A D | Kconfig | 50 Failure reports will BUG() in the hypervisor. This is intended for 51 local EL2 hypervisor development. 56 bool "Protected KVM hypervisor stacktraces" 60 Say Y here to enable pKVM hypervisor stacktraces on hyp_panic()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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/Documentation/virt/coco/ |
| H A D | sev-guest.rst | 10 The SEV API is a set of ioctls that are used by the guest or hypervisor 30 hypervisor or guest. The ioctl can be used inside the guest or the 31 hypervisor. 131 The certificate data returned is being provided by the hypervisor through the 147 :Type: hypervisor ioctl cmd 158 :Type: hypervisor ioctl cmd 169 :Type: hypervisor ioctl cmd 182 :Type: hypervisor ioctl cmd 210 being generated due to changes in validation state if the hypervisor tries 212 - Attempts to bypass PSP checks by the hypervisor by using a normal page, or
|
| /linux/Documentation/virt/kvm/ |
| H A 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
|
| /linux/arch/sparc/mm/ |
| H A 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/arch/powerpc/kvm/ |
| H A D | Kconfig | 80 tristate "KVM for POWER7 and later using hypervisor mode in host" 88 hypervisor mode available to the host. 101 tristate "KVM support without using hypervisor mode in host" 107 without using hypervisor mode in the host, by running the 114 This is not as fast as using hypervisor mode, but works on 115 machines where hypervisor mode is not available or not usable, 143 bool "Detailed timing for hypervisor real-mode code (for POWER8)" 177 Perf events give an overview of hypervisor performance overall
|
| /linux/Documentation/driver-api/virtio/ |
| H A D | virtio.rst | 15 for paravirtualized devices implemented by a hypervisor, it can be used 20 devices provided by the hypervisor, which exposes them as virtio devices 28 hypervisor, they're exposed to the guest as if they are physical devices 35 the hypervisor is done through shared memory (that's what makes virtio 61 specifically, the trigger will be an interrupt issued by the hypervisor 78 the hypervisor defines it. Taking the `QEMU virtio-console
|
| /linux/Documentation/networking/ |
| H A 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 115 net_failover also enables hypervisor controlled live migration to be supported 120 the source hypervisor. Note: It is assumed that the VM is connected to a 168 On the destination hypervisor, a shared bridge 'br0' is created before migration 172 The following script is executed on the destination hypervisor once migration
|
| /linux/net/vmw_vsock/ |
| H A D | Kconfig | 10 allowing communication between Virtual Machines and hypervisor 13 You should also select one or more hypervisor-specific transports 48 hypervisor.
|
| /linux/arch/sparc/kernel/ |
| H A D | smp_64.c | 110 if (tlb_type == hypervisor) in smp_callin() 359 if (tlb_type == hypervisor) { in smp_boot_one_cpu() 944 if (tlb_type == hypervisor) in smp_flush_dcache_folio_impl() 990 if (tlb_type == hypervisor) in flush_dcache_folio_all() 1040 if (tlb_type == hypervisor && in smp_fetch_global_pmu() 1280 if (tlb_type != hypervisor) in __cpu_up() 1295 if (tlb_type == hypervisor) { in cpu_play_dead() 1459 if (tlb_type != hypervisor) in smp_init_cpu_poke() 1493 if (tlb_type == hypervisor) { in smp_send_stop() 1561 if (tlb_type == hypervisor) in setup_per_cpu_areas()
|
| H A 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()
|
| /linux/Documentation/virt/hyperv/ |
| H A D | coco.rst | 8 face of a hypervisor/VMM that has been compromised and may behave maliciously. 72 and must be trusted by the guest OS. By implication, the hypervisor/VMM must 132 happens in the paravisor in the guest context (instead of the hypervisor/VMM 141 hypervisor/VMM. This is done via callbacks invoked from 145 that the paravisor can coordinate the transitions and inform the hypervisor 148 * Interrupt injection. In fully enlightened mode, a malicious hypervisor 161 directly to the hypervisor, just as in a non-CoCo VM. But in paravisor mode, 163 hypervisor. But the paravisor is idiosyncratic in this regard, and a few 165 hypervisor. These hypercall sites test for a paravisor being present, and use 238 the untrusted host partition and the untrusted hypervisor. Instead, the guest [all …]
|
| /linux/drivers/hv/ |
| H A D | Kconfig | 6 bool "Microsoft Hyper-V core hypervisor support" 25 Virtual Secure Mode (VSM) is a set of hypervisor capabilities and 72 # The hypervisor interface operates on 4k pages. Enforcing it here 74 # e.g. When withdrawing memory, the hypervisor gives back 4k pages in
|