| /dports/emulators/qemu-guest-agent/qemu-5.0.1/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 …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 menuconfig KVM config
21 bool "Kernel-based Virtual Machine (KVM) support"
48 if KVM
52 endif # KVM
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 menuconfig KVM config
21 bool "Kernel-based Virtual Machine (KVM) support"
48 if KVM
52 endif # KVM
|
| /dports/multimedia/libv4l/linux-5.13-rc2/arch/arm64/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 menuconfig KVM config
21 bool "Kernel-based Virtual Machine (KVM) support"
48 if KVM
52 endif # KVM
|
| /dports/emulators/qemu/qemu-6.2.0/docs/system/i386/ |
| H A D | kvm-pv.rst | 1 Paravirtualized KVM features
7 In some cases when implementing hardware interfaces in software is slow, ``KVM``
13 Paravirtualized ``KVM`` features are represented as CPU flags. The following
14 features are enabled by default for any CPU model when ``KVM`` acceleration is
28 paravirtualized ``KVM`` features to the guest.
34 Expose a ``KVM`` specific paravirtualized clocksource to the guest. Supported
46 Note: since Linux v5.10 the feature is deprecated and not enabled by ``KVM``.
92 Note, by default, ``KVM`` allows the guest to use all currently supported
|
| /dports/emulators/qemu/qemu-6.2.0/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 …]
|
| /dports/emulators/qemu60/qemu-6.0.0/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 …]
|
| /dports/emulators/qemu5/qemu-5.2.0/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 …]
|
| /dports/emulators/qemu-devel/qemu-de8ed1055c2ce18c95f597eb10df360dcb534f99/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 …]
|
| /dports/emulators/qemu42/qemu-4.2.1/hw/intc/ |
| H A D | Kconfig | 28 depends on ARM_GIC && KVM
33 depends on OPENPIC && KVM
46 depends on XICS && KVM
57 depends on S390_FLIC && KVM
|
| /dports/emulators/qemu-utils/qemu-4.2.1/hw/intc/ |
| H A D | Kconfig | 28 depends on ARM_GIC && KVM
33 depends on OPENPIC && KVM
46 depends on XICS && KVM
57 depends on S390_FLIC && KVM
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm.sh | 25 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
26 PATH=${KVM}/bin:$PATH; export PATH
33 TORTURE_INITRD="$KVM/initrd"; export TORTURE_INITRD
251 CONFIGFRAG=${KVM}/configs/${TORTURE_SUITE}; export CONFIGFRAG
261 resdir=$KVM/res
375 KVM="$KVM"; export KVM
425 -v KVM="$KVM" \
|
| /dports/multimedia/libv4l/linux-5.13-rc2/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm.sh | 25 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
26 PATH=${KVM}/bin:$PATH; export PATH
33 TORTURE_INITRD="$KVM/initrd"; export TORTURE_INITRD
251 CONFIGFRAG=${KVM}/configs/${TORTURE_SUITE}; export CONFIGFRAG
261 resdir=$KVM/res
375 KVM="$KVM"; export KVM
425 -v KVM="$KVM" \
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm.sh | 25 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
26 PATH=${KVM}/bin:$PATH; export PATH
33 TORTURE_INITRD="$KVM/initrd"; export TORTURE_INITRD
251 CONFIGFRAG=${KVM}/configs/${TORTURE_SUITE}; export CONFIGFRAG
261 resdir=$KVM/res
375 KVM="$KVM"; export KVM
425 -v KVM="$KVM" \
|
| /dports/emulators/qemu-guest-agent/qemu-5.0.1/hw/intc/ |
| H A D | Kconfig | 31 depends on ARM_GIC && KVM
36 depends on OPENPIC && KVM
49 depends on XICS && KVM
60 depends on S390_FLIC && KVM
|
| /dports/emulators/qemu-cheri/qemu-0a323821042c36e21ea80e58b9545dfc3b0cb8ef/hw/intc/ |
| H A D | Kconfig | 31 depends on ARM_GIC && KVM
36 depends on OPENPIC && KVM
49 depends on XICS && KVM
60 depends on S390_FLIC && KVM
|
| /dports/net/hostapd-devel/hostap-14ab4a816/tests/hwsim/vm/ |
| H A D | vm-run.sh | 119 unset KVM
121 KVM=kvm
124 KVM=$kvmprog
139 if [ -z $KVM ]; then
159 if [ -z $KVM ]; then
172 $KVM \
|
| /dports/security/wpa_supplicant-devel/hostap-14ab4a816/tests/hwsim/vm/ |
| H A D | vm-run.sh | 119 unset KVM
121 KVM=kvm
124 KVM=$kvmprog
139 if [ -z $KVM ]; then
159 if [ -z $KVM ]; then
172 $KVM \
|
| /dports/emulators/qemu5/qemu-5.2.0/hw/intc/ |
| H A D | Kconfig | 31 depends on ARM_GIC && KVM
36 depends on OPENPIC && KVM
49 depends on XICS && KVM
60 depends on S390_FLIC && KVM
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/admin-guide/hw-vuln/ |
| H A D | multihit.rst | 81 * - KVM: Mitigation: Split huge pages
83 * - KVM: Mitigation: VMX unsupported
85 * - KVM: Mitigation: VMX disabled
86 - KVM is not vulnerable because Virtual Machine Extensions (VMX) is disabled.
87 * - KVM: Vulnerable
111 In order to mitigate the vulnerability, KVM initially marks all huge pages
115 If EPT is disabled or not available on the host, KVM is in control of TLB
119 (non-nested) page tables. For simplicity, KVM will make large pages
122 Mitigation control on the kernel command line and KVM - module parameter
125 The KVM hypervisor mitigation mechanism for marking huge pages as
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/admin-guide/hw-vuln/ |
| H A D | multihit.rst | 81 * - KVM: Mitigation: Split huge pages
83 * - KVM: Mitigation: VMX unsupported
85 * - KVM: Mitigation: VMX disabled
86 - KVM is not vulnerable because Virtual Machine Extensions (VMX) is disabled.
87 * - KVM: Vulnerable
111 In order to mitigate the vulnerability, KVM initially marks all huge pages
115 If EPT is disabled or not available on the host, KVM is in control of TLB
119 (non-nested) page tables. For simplicity, KVM will make large pages
122 Mitigation control on the kernel command line and KVM - module parameter
125 The KVM hypervisor mitigation mechanism for marking huge pages as
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/admin-guide/hw-vuln/ |
| H A D | multihit.rst | 81 * - KVM: Mitigation: Split huge pages
83 * - KVM: Mitigation: VMX unsupported
85 * - KVM: Mitigation: VMX disabled
86 - KVM is not vulnerable because Virtual Machine Extensions (VMX) is disabled.
87 * - KVM: Vulnerable
111 In order to mitigate the vulnerability, KVM initially marks all huge pages
115 If EPT is disabled or not available on the host, KVM is in control of TLB
119 (non-nested) page tables. For simplicity, KVM will make large pages
122 Mitigation control on the kernel command line and KVM - module parameter
125 The KVM hypervisor mitigation mechanism for marking huge pages as
[all …]
|
| /dports/emulators/qemu42/qemu-4.2.1/docs/ |
| H A D | arm-cpu-features.rst | 33 when using the KVM accelerator and when running on a host CPU type that
62 all SVE vector lengths can be supported, when KVM is in use it's more
126 A note about CPU models and KVM
129 Named CPU models generally do not work with KVM. There are a few cases
130 that do work, e.g. using the named CPU model `cortex-a57` with KVM on a
131 seattle host, but mostly if KVM is enabled the `host` CPU type must be
146 above, the `cortex-a57` CPU type is also valid when KVM is enabled.
151 some time. Additionally, if the KVM-enabled QEMU instance running on a
194 2) If a vector length `N` is enabled, then, when KVM is enabled, all
197 lengths must be enabled. E.g. with KVM if the host supports all
[all …]
|
| /dports/emulators/qemu-utils/qemu-4.2.1/docs/ |
| H A D | arm-cpu-features.rst | 33 when using the KVM accelerator and when running on a host CPU type that
62 all SVE vector lengths can be supported, when KVM is in use it's more
126 A note about CPU models and KVM
129 Named CPU models generally do not work with KVM. There are a few cases
130 that do work, e.g. using the named CPU model `cortex-a57` with KVM on a
131 seattle host, but mostly if KVM is enabled the `host` CPU type must be
146 above, the `cortex-a57` CPU type is also valid when KVM is enabled.
151 some time. Additionally, if the KVM-enabled QEMU instance running on a
194 2) If a vector length `N` is enabled, then, when KVM is enabled, all
197 lengths must be enabled. E.g. with KVM if the host supports all
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/arch/powerpc/kvm/ |
| H A D | Makefile | 7 KVM := ../../../virt/kvm macro
9 common-objs-y = $(KVM)/kvm_main.o $(KVM)/eventfd.o
10 common-objs-$(CONFIG_KVM_VFIO) += $(KVM)/vfio.o
11 common-objs-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o
126 kvm-objs-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o
|