| /OK3568_Linux_fs/buildroot/package/kvmtool/ |
| H A D | Config.in | 15 kvmtool is a lightweight tool for hosting KVM guests. 16 As a pure virtualization tool it only supports guests using 18 guests on those 64-bit architectures that allow this.
|
| /OK3568_Linux_fs/kernel/drivers/vhost/ |
| H A D | Kconfig | 48 for use with virtio-scsi guests 58 sockets for communicating with guests. The guests must have the 81 This option allows vhost to support guests with a different byte
|
| /OK3568_Linux_fs/kernel/fs/vboxsf/ |
| H A D | Kconfig | 6 VirtualBox hosts can share folders with guests, this driver 10 If you want to use shared folders in VirtualBox guests, answer Y or M.
|
| /OK3568_Linux_fs/kernel/arch/mips/kvm/ |
| H A D | Kconfig | 11 other operating systems inside virtual machines (guests). 42 Use trap and emulate to virtualize 32-bit guests in user mode. This 51 Use the MIPS Virtualization (VZ) ASE to virtualize guests. This
|
| /OK3568_Linux_fs/kernel/drivers/staging/unisys/Documentation/ABI/ |
| H A D | sysfs-platform-visorchipset | 64 situation by sending a message to guests using these VFs, and 66 another message is sent to the guests to re-enable the VFs. 83 situation by sending a message to guests using these VFs, and 85 another message is sent to the guests to re-enable the VFs.
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/ |
| H A D | nested-vmx.rst | 11 to easily and efficiently run guest operating systems. Normally, these guests 12 *cannot* themselves be hypervisors running their own guests, because in VMX, 13 guests cannot use VMX instructions. 16 hypervisors (which use VMX) with their own nested guests. It does so by 31 Single-level virtualization has two levels - the host (KVM) and the guests.
|
| H A D | running-nested-guests.rst | 2 Running nested guests with KVM 61 multiple nested guests (level-2 guests), running different OSes, on 64 - Live migration of "guest hypervisors" and their nested guests, for 197 actually running L2 guests, is expected to function normally even on AMD 198 systems but may fail once guests are started.
|
| H A D | index.rst | 32 running-nested-guests
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/arm64/fp/ |
| H A D | README | 68 should be run in parallel in two KVM guests, while simultaneously 71 1) Start 2 guests, using the following command for each: 83 allows multiple guests to be run in parallel while running other
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A D | virtiofs.rst | 18 Use cases include making files available to new guests during installation, 20 stateless or ephemeral guests, and sharing a directory between guests.
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-hypervisor-xen | 26 and all other guests. Only available to 27 privileged guests.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/ |
| H A D | l1tf.rst | 219 guests affine to one or more physical cores. The proper mechanism for 223 If only a single guest or related guests run on sibling SMT threads on 235 **Note**, that assigning guests to a fixed set of physical cores affects 241 For further information about confining guests to a single or to a group 258 which run untrusted guests, reduces the attack vector space. 261 guests, provide interesting data for an attacker depends on the system 282 of other mitigation solutions like confining guests to dedicated cores. 352 with SMT enabled, because the effective page tables for guests are 459 2. Virtualization with trusted guests 472 3. Virtualization with untrusted guests [all …]
|
| H A D | tsx_async_abort.rst | 73 applications running on hosts or guests. 250 1. Trusted userspace and guests 255 disabled. The same applies to virtualized environments with trusted guests. 258 2. Untrusted userspace and guests 261 If there are untrusted applications or guests on the system, enabling TSX
|
| H A D | multihit.rst | 63 guests in a virtualized system. 156 2. Virtualization with trusted guests 163 3. Virtualization with untrusted guests
|
| H A D | spectre.rst | 279 For Spectre variant 1 attacks, rogue guests can pass parameters 285 For Spectre variant 2 attacks, rogue guests can :ref:`poison 292 guests from affecting indirect branching in the host kernel. 294 To protect host processes from rogue guests, host processes can have 305 between guests. This may be done via mechanisms such as shared memory 315 Linux kernel mitigates attacks to other guests running in the same 531 Within the kernel, Spectre variant 1 attacks from rogue guests are 537 For Spectre variant 2 attacks from rogue guests to the kernel, the 539 poisoned entries in branch target buffer left by rogue guests. It also 542 or attacker guests leaving poisoned entries in the return stack buffer. [all …]
|
| /OK3568_Linux_fs/kernel/fs/fuse/ |
| H A D | Kconfig | 36 The Virtio Filesystem allows guests to mount file systems from the 39 If you want to share files between guests or with the host, answer Y
|
| /OK3568_Linux_fs/kernel/Documentation/powerpc/ |
| H A D | dawr-power9.rst | 30 guest on a POWER9 host. Current Linux guests ignore this error, so 48 The same will also be true for any guests started on a POWER9 81 inconsistent view of what's available. Similarly for guests.
|
| /OK3568_Linux_fs/kernel/drivers/xen/ |
| H A D | Kconfig | 106 For example, by reading and writing the "xenbus" file, guests 190 PCI devices to other guests. If you select this to be a module, you 192 you want to make visible to other guests. 232 to other guests via a high-performance shared-memory interface. 234 if guests need generic access to SCSI devices. 308 Support for auto-translated physmap guests.
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/arm/ |
| H A D | pvtime.rst | 7 support for AArch64 guests: 21 paravirtualized time is not available to 32 bit Arm guests. The existence of
|
| /OK3568_Linux_fs/kernel/Documentation/s390/ |
| H A D | vfio-ap.rst | 14 is to make AP cards available to KVM guests using the VFIO mediated device 168 This is valid because both guests have a unique set of APQNs: 177 This is also valid because both guests have a unique set of APQNs: 186 This is an invalid configuration because both guests have access to 201 1. Provides the interfaces to secure APQNs for exclusive use of KVM guests. 210 Reserve APQNs for exclusive use of KVM guests 459 Let's now provide an example to illustrate how KVM guests may be given 461 three guests such that executing the lszcrypt command on the guests would 531 2. Secure the AP queues to be used by the three guests so that the host can not 682 three guests and to provide an interface to the vfio_ap driver for [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/misc/ |
| H A D | pvpanic-mmio.txt | 9 QEMU exposes the data register to guests as memory mapped registers.
|
| /OK3568_Linux_fs/kernel/drivers/visorbus/ |
| H A D | Kconfig | 11 Virtualized devices allow Linux guests on a system to share disks and
|
| /OK3568_Linux_fs/kernel/net/iucv/ |
| H A D | Kconfig | 9 communication link between VM guests.
|
| /OK3568_Linux_fs/kernel/tools/perf/util/ |
| H A D | build-id.c | 379 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__write_buildid_table() 413 for (nd = rb_first_cached(&session->machines.guests); nd; in dsos__hit_all() 882 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__cache_build_ids() 900 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__read_build_ids()
|
| /OK3568_Linux_fs/yocto/meta-qt5/recipes-qt/qt5/ |
| H A D | qt5-plugin-generic-vboxtouch_git.bb | 1 DESCRIPTION = "This driver extends Qt's platform support (QPA) for Virtualbox guests. \
|