Searched full:hypervisors (Results 1 – 20 of 20) sorted by relevance
| /Documentation/virt/ |
| D | paravirt_ops.rst | 9 different hypervisors; this restriction was removed with pv_ops.
11 hypervisors. It allows each hypervisor to override critical operations and
13 including native machine -- without any hypervisors.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | pkvm,pviommu.yaml | 13 hypervisors with a small TCB as in confidential computing to implement
16 KVM specific interface, so it can be implemented by other hypervisors
|
| /Documentation/admin-guide/hw-vuln/ |
| D | vmscape.rst | 7 prediction in host userspace. It particularly affects hypervisors like QEMU.
49 because nested hypervisors should already be deploying IBPB to isolate
55 When Simultaneous Multi-Threading (SMT) is enabled, hypervisors can be
|
| D | l1tf.rst | 373 the hypervisors, i.e. unconditional L1D flushing
376 is still possible after boot. Hypervisors will issue a
389 is still possible after boot. Hypervisors will issue a
398 is still possible after boot. Hypervisors will issue a
403 flush,nowarn Same as 'flush', but hypervisors will not warn when a VM is
|
| /Documentation/virt/kvm/x86/ |
| D | nested-vmx.rst | 12 *cannot* themselves be hypervisors running their own guests, because in VMX,
16 hypervisors (which use VMX) with their own nested guests. It does so by
63 which are used in practice by popular hypervisors (KVM and others).
|
| D | running-nested-guests.rst | 66 - Live migration of "guest hypervisors" and their nested guests, for
|
| /Documentation/devicetree/bindings/rng/ |
| D | microsoft,vmgenid.yaml | 13 Firmwares or hypervisors can use this devicetree to describe an
|
| /Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 9 hypervisors.
35 documentation for the s390 hypervisors defining them.
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 39 Linux hypervisors.
|
| /Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 6 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 173 * enabling firmware and hypervisors to support existing and new kernels.
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic-its.rst | 149 interrupts for nested hypervisors.
|
| /Documentation/accel/qaic/ |
| D | qaic.rst | 45 (circa 2023). Between hypervisors masking the PCIe MSI capability structure to
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 89 operations; hypervisors never directly cause the movement of message data.
|
| /Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 120 The standard H extension for hypervisors as ratified in the 20191213
|
| /Documentation/arch/sparc/oradax/ |
| D | oracle-dax.rst | 132 Hypervisors might return 'notfound' when the CCB is in 'inprogress'
|
| /Documentation/arch/powerpc/ |
| D | papr_hcalls.rst | 13 privileged operations. Currently there are two PAPR compliant hypervisors:
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 491 done by virtio-mem or by some hypervisors
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 850 both Xen and PowerPC hypervisors.
2727 hypervisors that want to "own" virtualization hardware.
2919 hypervisors, i.e. unconditional L1D flush.
2923 boot. Hypervisors will issue a warning
2941 boot. Hypervisors will issue a warning
2953 boot. Hypervisors will issue a warning
2959 Same as 'flush', but hypervisors will not
|
| /Documentation/virt/kvm/ |
| D | api.rst | 7952 This capability is enabled for hypervisors on platforms like POWER9
|