Home
last modified time | relevance | path

Searched refs:guests (Results 1 – 25 of 64) sorted by relevance

123

/Linux-v5.4/drivers/vhost/
DKconfig21 for use with virtio-scsi guests
31 sockets for communicating with guests. The guests must have the
47 This option allows vhost to support guests with a different byte
/Linux-v5.4/arch/mips/kvm/
DKconfig11 other operating systems inside virtual machines (guests).
40 Use trap and emulate to virtualize 32-bit guests in user mode. This
49 Use the MIPS Virtualization (VZ) ASE to virtualize guests. This
/Linux-v5.4/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset64 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.
/Linux-v5.4/fs/fuse/
DKconfig36 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
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-hypervisor-xen24 and all other guests. Only available to
25 privileged guests.
/Linux-v5.4/Documentation/filesystems/
Dvirtiofs.rst16 Use cases include making files available to new guests during installation,
18 stateless or ephemeral guests, and sharing a directory between guests.
/Linux-v5.4/Documentation/virt/kvm/
Dnested-vmx.txt8 to easily and efficiently run guest operating systems. Normally, these guests
9 *cannot* themselves be hypervisors running their own guests, because in VMX,
10 guests cannot use VMX instructions.
13 hypervisors (which use VMX) with their own nested guests. It does so by
28 Single-level virtualization has two levels - the host (KVM) and the guests.
Damd-memory-encryption.rst23 Bits[31:0] Number of encrypted guests supported simultaneously
44 Hence, the ASID for the SEV-enabled guests must be from 1 to a maximum value
57 guests, such as launching, running, snapshotting, migrating and decommissioning.
/Linux-v5.4/Documentation/powerpc/
Ddawr-power9.rst30 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.
/Linux-v5.4/Documentation/admin-guide/hw-vuln/
Dl1tf.rst219 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 …]
Dtsx_async_abort.rst73 applications running on hosts or guests.
249 1. Trusted userspace and guests
254 disabled. The same applies to virtualized environments with trusted guests.
257 2. Untrusted userspace and guests
260 If there are untrusted applications or guests on the system, enabling TSX
Dmultihit.rst63 guests in a virtualized system.
152 2. Virtualization with trusted guests
159 3. Virtualization with untrusted guests
Dspectre.rst266 For Spectre variant 1 attacks, rogue guests can pass parameters
272 For Spectre variant 2 attacks, rogue guests can :ref:`poison
279 guests from affecting indirect branching in the host kernel.
281 To protect host processes from rogue guests, host processes can have
292 between guests. This may be done via mechanisms such as shared memory
302 Linux kernel mitigates attacks to other guests running in the same
508 Within the kernel, Spectre variant 1 attacks from rogue guests are
514 For Spectre variant 2 attacks from rogue guests to the kernel, the
516 poisoned entries in branch target buffer left by rogue guests. It also
519 or attacker guests leaving poisoned entries in the return stack buffer.
[all …]
/Linux-v5.4/drivers/xen/
DKconfig104 For example, by reading and writing the "xenbus" file, guests
186 PCI devices to other guests. If you select this to be a module, you
188 you want to make visible to other guests.
228 to other guests via a high-performance shared-memory interface.
230 if guests need generic access to SCSI devices.
304 Support for auto-translated physmap guests.
/Linux-v5.4/Documentation/devicetree/bindings/misc/
Dpvpanic-mmio.txt9 QEMU exposes the data register to guests as memory mapped registers.
/Linux-v5.4/drivers/visorbus/
DKconfig11 Virtualized devices allow Linux guests on a system to share disks and
/Linux-v5.4/net/iucv/
DKconfig9 communication link between VM guests.
/Linux-v5.4/Documentation/s390/
Dvfio-ap.rst14 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 …]
/Linux-v5.4/tools/perf/util/
Dmachine.c251 machines->guests = RB_ROOT_CACHED; in machines__init()
263 struct rb_node **p = &machines->guests.rb_root.rb_node; in machines__add()
288 rb_insert_color_cached(&machine->rb_node, &machines->guests, leftmost); in machines__add()
299 for (nd = rb_first_cached(&machines->guests); nd; nd = rb_next(nd)) { in machines__set_comm_exec()
308 struct rb_node **p = &machines->guests.rb_root.rb_node; in machines__find()
371 for (nd = rb_first_cached(&machines->guests); nd; nd = rb_next(nd)) { in machines__process_guests()
384 for (node = rb_first_cached(&machines->guests); node; in machines__set_id_hdr_size()
833 for (nd = rb_first_cached(&machines->guests); nd; nd = rb_next(nd)) { in machines__fprintf_dsos()
853 for (nd = rb_first_cached(&machines->guests); nd; nd = rb_next(nd)) { in machines__fprintf_dsos_buildid()
1203 struct rb_node *next = rb_first_cached(&machines->guests); in machines__destroy_kernel_maps()
[all …]
Dbuild-id.c372 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__write_buildid_table()
406 for (nd = rb_first_cached(&session->machines.guests); nd; in dsos__hit_all()
860 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__cache_build_ids()
878 for (nd = rb_first_cached(&session->machines.guests); nd; in perf_session__read_build_ids()
/Linux-v5.4/arch/arm/kvm/
DKconfig13 other operating systems inside virtual machines (guests).
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt10 QEMU exposes the control and data register to ARM guests as memory mapped
/Linux-v5.4/arch/arm64/kvm/
DKconfig13 other operating systems inside virtual machines (guests).
/Linux-v5.4/arch/arm/boot/dts/
Dxenvm-4.2.dts3 * Xen Virtual Machine for unprivileged guests
/Linux-v5.4/arch/s390/kvm/
DKconfig12 operating systems inside virtual machines (guests).

123