| /dports/multimedia/v4l-utils/linux-5.13-rc2/arch/powerpc/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 config KVM config
52 tristate "KVM support for PowerPC book3s_32 processors"
54 select KVM
71 select KVM
149 bool "KVM support for PowerPC E500v2 processors"
151 select KVM
166 select KVM
180 bool "KVM in-kernel MPIC emulation"
181 depends on KVM && E500
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/arch/powerpc/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 config KVM config
52 tristate "KVM support for PowerPC book3s_32 processors"
54 select KVM
71 select KVM
149 bool "KVM support for PowerPC E500v2 processors"
151 select KVM
166 select KVM
180 bool "KVM in-kernel MPIC emulation"
181 depends on KVM && E500
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/arch/powerpc/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 config KVM config
52 tristate "KVM support for PowerPC book3s_32 processors"
54 select KVM
71 select KVM
149 bool "KVM support for PowerPC E500v2 processors"
151 select KVM
166 select KVM
180 bool "KVM in-kernel MPIC emulation"
181 depends on KVM && E500
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/virt/kvm/ |
| H A D | running-nested-guests.rst | 2 Running nested guests with KVM
7 example is a KVM guest that in turn runs on a KVM guest (the rest of
18 | KVM (/dev/kvm) |
29 - L0 – level-0; the bare metal host, running KVM
32 hypervisor", as it itself is capable of running KVM.
87 the KVM modules::
105 4. Unload and re-load the KVM Intel module::
157 nested guest with accelerated KVM.
182 Live migration with nested KVM
223 - Ensure you are actually running KVM on KVM. Sometimes people do not
[all …]
|
| H A D | s390-diag.rst | 4 The s390 DIAGNOSE call on KVM
7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
34 DIAGNOSE function codes not specific to KVM, please refer to the
38 DIAGNOSE function code 'X'500' - KVM virtio functions
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
62 Handled by either userspace or KVM (ioeventfd case).
69 General register 4 contains a 64bit identifier for KVM usage (the
80 DIAGNOSE function code 'X'501 - KVM breakpoint
[all …]
|
| H A D | s390-pv.rst | 9 Protected virtual machines (PVM) are KVM VMs that do not allow KVM to
12 provides an API that can be used by PVMs and KVM to request management
16 transition into protected mode. On transition, KVM registers the guest
34 Interrupt injection is safeguarded by the Ultravisor. As KVM doesn't
47 been intercepted into KVM. The exceptions need to be a valid outcome
48 of an instruction emulation by KVM, e.g. we can never inject a
49 addressing exception as they are reported by SIE since KVM has no
55 KVM cannot intercept lctl(g) and lpsw(e) anymore in order to be
67 to interpret every instruction, but needs to hand some tasks to KVM;
106 The notification type intercepts inform KVM about guest environment
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/virt/kvm/ |
| H A D | running-nested-guests.rst | 2 Running nested guests with KVM
7 example is a KVM guest that in turn runs on a KVM guest (the rest of
18 | KVM (/dev/kvm) |
29 - L0 – level-0; the bare metal host, running KVM
32 hypervisor", as it itself is capable of running KVM.
87 the KVM modules::
105 4. Unload and re-load the KVM Intel module::
157 nested guest with accelerated KVM.
182 Live migration with nested KVM
223 - Ensure you are actually running KVM on KVM. Sometimes people do not
[all …]
|
| H A D | s390-diag.rst | 4 The s390 DIAGNOSE call on KVM
7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
34 DIAGNOSE function codes not specific to KVM, please refer to the
38 DIAGNOSE function code 'X'500' - KVM virtio functions
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
62 Handled by either userspace or KVM (ioeventfd case).
69 General register 4 contains a 64bit identifier for KVM usage (the
80 DIAGNOSE function code 'X'501 - KVM breakpoint
[all …]
|
| H A D | s390-pv.rst | 9 Protected virtual machines (PVM) are KVM VMs that do not allow KVM to
12 provides an API that can be used by PVMs and KVM to request management
16 transition into protected mode. On transition, KVM registers the guest
34 Interrupt injection is safeguarded by the Ultravisor. As KVM doesn't
47 been intercepted into KVM. The exceptions need to be a valid outcome
48 of an instruction emulation by KVM, e.g. we can never inject a
49 addressing exception as they are reported by SIE since KVM has no
55 KVM cannot intercept lctl(g) and lpsw(e) anymore in order to be
67 to interpret every instruction, but needs to hand some tasks to KVM;
106 The notification type intercepts inform KVM about guest environment
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/virt/kvm/ |
| H A D | running-nested-guests.rst | 2 Running nested guests with KVM
7 example is a KVM guest that in turn runs on a KVM guest (the rest of
18 | KVM (/dev/kvm) |
29 - L0 – level-0; the bare metal host, running KVM
32 hypervisor", as it itself is capable of running KVM.
87 the KVM modules::
105 4. Unload and re-load the KVM Intel module::
157 nested guest with accelerated KVM.
182 Live migration with nested KVM
223 - Ensure you are actually running KVM on KVM. Sometimes people do not
[all …]
|
| H A D | s390-diag.rst | 4 The s390 DIAGNOSE call on KVM
7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
34 DIAGNOSE function codes not specific to KVM, please refer to the
38 DIAGNOSE function code 'X'500' - KVM virtio functions
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
62 Handled by either userspace or KVM (ioeventfd case).
69 General register 4 contains a 64bit identifier for KVM usage (the
80 DIAGNOSE function code 'X'501 - KVM breakpoint
[all …]
|
| H A D | s390-pv.rst | 9 Protected virtual machines (PVM) are KVM VMs that do not allow KVM to
12 provides an API that can be used by PVMs and KVM to request management
16 transition into protected mode. On transition, KVM registers the guest
34 Interrupt injection is safeguarded by the Ultravisor. As KVM doesn't
47 been intercepted into KVM. The exceptions need to be a valid outcome
48 of an instruction emulation by KVM, e.g. we can never inject a
49 addressing exception as they are reported by SIE since KVM has no
55 KVM cannot intercept lctl(g) and lpsw(e) anymore in order to be
67 to interpret every instruction, but needs to hand some tasks to KVM;
106 The notification type intercepts inform KVM about guest environment
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/virt/kvm/arm/ |
| H A D | psci.rst | 7 KVM implements the PSCI (Power State Coordination Interface)
12 and KVM implements these updates if they make sense from a virtualization
15 This means that a guest booted on two different versions of KVM can
21 In order to remedy this situation, KVM exposes a set of "firmware
33 highest PSCI version implemented by KVM and compatible with v0.2)
34 - Allows any PSCI version implemented by KVM and compatible with
40 offered by KVM to the guest via a HVC call. The workaround is described
46 KVM does not offer
58 offered by KVM to the guest via a HVC call. The workaround is described
65 available. KVM does not offer firmware support for the workaround.
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/virt/kvm/arm/ |
| H A D | psci.rst | 7 KVM implements the PSCI (Power State Coordination Interface)
12 and KVM implements these updates if they make sense from a virtualization
15 This means that a guest booted on two different versions of KVM can
21 In order to remedy this situation, KVM exposes a set of "firmware
33 highest PSCI version implemented by KVM and compatible with v0.2)
34 - Allows any PSCI version implemented by KVM and compatible with
40 offered by KVM to the guest via a HVC call. The workaround is described
46 KVM does not offer
58 offered by KVM to the guest via a HVC call. The workaround is described
65 available. KVM does not offer firmware support for the workaround.
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/virt/kvm/arm/ |
| H A D | psci.rst | 7 KVM implements the PSCI (Power State Coordination Interface)
12 and KVM implements these updates if they make sense from a virtualization
15 This means that a guest booted on two different versions of KVM can
21 In order to remedy this situation, KVM exposes a set of "firmware
33 highest PSCI version implemented by KVM and compatible with v0.2)
34 - Allows any PSCI version implemented by KVM and compatible with
40 offered by KVM to the guest via a HVC call. The workaround is described
46 KVM does not offer
58 offered by KVM to the guest via a HVC call. The workaround is described
65 available. KVM does not offer firmware support for the workaround.
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Makefile | 8 KVM=../../../virt/kvm macro
13 kvm-y := $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o \
14 $(KVM)/vfio.o $(KVM)/irqchip.o \
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Makefile | 8 KVM=../../../virt/kvm macro
13 kvm-y := $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o \
14 $(KVM)/vfio.o $(KVM)/irqchip.o \
|
| /dports/multimedia/libv4l/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Makefile | 8 KVM=../../../virt/kvm macro
13 kvm-y := $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o \
14 $(KVM)/vfio.o $(KVM)/irqchip.o \
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 14 are enabled and disabled for use by the VM, KVM should be updated
15 about their presence. When registered with KVM, a reference to the
16 VFIO-group is held by KVM.
22 KVM_DEV_VFIO_GROUP_ADD: Add a VFIO group to VFIO-KVM device tracking
25 KVM_DEV_VFIO_GROUP_DEL: Remove a VFIO group from VFIO-KVM device tracking
29 allocated by sPAPR KVM.
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 14 are enabled and disabled for use by the VM, KVM should be updated
15 about their presence. When registered with KVM, a reference to the
16 VFIO-group is held by KVM.
22 KVM_DEV_VFIO_GROUP_ADD: Add a VFIO group to VFIO-KVM device tracking
25 KVM_DEV_VFIO_GROUP_DEL: Remove a VFIO group from VFIO-KVM device tracking
29 allocated by sPAPR KVM.
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 14 are enabled and disabled for use by the VM, KVM should be updated
15 about their presence. When registered with KVM, a reference to the
16 VFIO-group is held by KVM.
22 KVM_DEV_VFIO_GROUP_ADD: Add a VFIO group to VFIO-KVM device tracking
25 KVM_DEV_VFIO_GROUP_DEL: Remove a VFIO group from VFIO-KVM device tracking
29 allocated by sPAPR KVM.
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/arch/s390/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
51 depends on KVM
53 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/arch/s390/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
51 depends on KVM
53 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
| /dports/multimedia/libv4l/linux-5.13-rc2/arch/s390/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
51 depends on KVM
53 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
| /dports/emulators/qemu-cheri/qemu-0a323821042c36e21ea80e58b9545dfc3b0cb8ef/docs/system/arm/ |
| H A D | cpu-features.rst | 27 when using the KVM accelerator and when running on a host CPU type that
28 supports the feature. While `aarch64` currently only works with KVM,
29 it could work with TCG. CPU features that are specific to KVM are
30 prefixed with "kvm-" and are described in "KVM VCPU Features".
58 all SVE vector lengths can be supported, when KVM is in use it's more
122 A note about CPU models and KVM
142 above, the `cortex-a57` CPU type is also valid when KVM is enabled.
170 KVM VCPU Features
173 KVM VCPU features are CPU features that are specific to KVM, such as
176 are named with the prefix "kvm-". KVM VCPU features may be probed,
[all …]
|