| /linux/include/xen/interface/ |
| H A D | xenpmu.h | 45 * - XENPMU_MODE_SELF: Guests can profile themselves
46 * - XENPMU_MODE_HV: Guests can profile themselves, dom0 profiles
49 * everyone: itself, the hypervisor and the guests.
77 * guests set to vcpu_id;
82 * Domain that was interrupted. On non-privileged guests set to
84 * On privileged guests can be DOMID_SELF, DOMID_XEN, or, when in
|
| H A D | sched.h | 38 * This legacy version is available to new guests as:
62 * x86 PV guests must also set RDX (EDX for 32-bit guests) to the MFN
|
| /linux/arch/x86/kvm/ |
| H A D | Kconfig | 13 operating systems inside virtual machines (guests).
108 bool "Check that guests do not receive #VE exceptions"
112 let guests receive a virtualization exception. Virtualization
127 Enables KVM guests to create SGX enclaves.
130 guests via a device node, e.g. /dev/sgx_vepc.
203 of Windows and Hyper-V guests on KVM.
211 Provides KVM support for the hosting Xen HVM guests and
|
| /linux/drivers/xen/ |
| H A D | Kconfig | 106 For example, by reading and writing the "xenbus" file, guests
196 device backend driver without para-virtualized support for guests.
199 other guests.
216 PCI devices to other guests. If you select this to be a module, you
218 you want to make visible to other guests.
258 to other guests via a high-performance shared-memory interface.
260 if guests need generic access to SCSI devices.
316 Support for auto-translated physmap guests.
370 Require virtio for Xen guests to use grant mappings.
|
| /linux/drivers/vhost/ |
| H A D | Kconfig | 54 for use with virtio-scsi guests
64 sockets for communicating with guests. The guests must have the
87 This option allows vhost to support guests with a different byte
|
| /linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 17 Guests often require access to files residing on the host or remote systems.
18 Use cases include making files available to new guests during installation,
20 stateless or ephemeral guests, and sharing a directory between guests.
|
| /linux/Documentation/virt/kvm/x86/ |
| 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 | 4 Running nested guests with KVM
63 multiple nested guests (level-2 guests), running different OSes, on
66 - Live migration of "guest hypervisors" and their nested guests, for
199 actually running L2 guests, is expected to function normally even on AMD
200 systems but may fail once guests are started.
|
| /linux/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 | gather_data_sampling.rst | 34 Guests can infer data from hosts
35 Guest can infer guest from other guests
39 lower-privilege contexts like guests and when running outside SGX enclaves.
42 that guests are not allowed to disable the GDS mitigation. If a host erred and
|
| H A D | indirect-target-selection.rst | 51 Cove (Alder Lake and Sapphire Rapids). This can help guests to determine the
97 Mitigation in guests
99 All guests deploy ITS mitigation by default, irrespective of eIBRS enumeration
104 To prevent guests from unnecessarily deploying the mitigation on unaffected
108 guests as per the host's affected status.
|
| H A D | tsx_async_abort.rst | 73 applications running on hosts or guests.
243 1. Trusted userspace and guests
248 disabled. The same applies to virtualized environments with trusted guests.
251 2. Untrusted userspace and guests
254 If there are untrusted applications or guests on the system, enabling TSX
|
| /linux/arch/x86/coco/tdx/ |
| H A D | tdcall.S | 13 * __tdcall() - Used by TDX guests to request services from the TDX
30 * __tdcall_ret() - Used by TDX guests to request services from the TDX
48 * __tdcall_saved_ret() - Used by TDX guests to request services from the
|
| /linux/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.
|
| /linux/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
|
| /linux/arch/x86/boot/ |
| H A D | io.h | 24 * TDX guests override these to use hypercalls.
35 * TDX guests override these callbacks with TDX-specific helpers.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | dawr-power9.rst | 38 guest on a POWER9 host. Current Linux guests ignore this error, so
56 The same will also be true for any guests started on a POWER9
89 inconsistent view of what's available. Similarly for guests.
|
| /linux/Documentation/arch/s390/ |
| H A D | vfio-ap-locking.rst | 54 The Guests Lock (drivers/s390/crypto/vfio_ap_private.h)
66 The Guests Lock (matrix_dev->guests_lock) controls access to the
88 It is not necessary to take the Guests Lock to access the KVM pointer if the
|
| H A D | vfio-ap.rst | 14 is to make AP cards available to KVM guests using the VFIO mediated device
165 This is valid because both guests have a unique set of APQNs:
174 This is also valid because both guests have a unique set of APQNs:
183 This is an invalid configuration because both guests have access to
198 1. Provides the interfaces to secure APQNs for exclusive use of KVM guests.
208 Reserve APQNs for exclusive use of KVM guests
529 Let's now provide an example to illustrate how KVM guests may be given
531 three guests such that executing the lszcrypt command on the guests would
598 2. Secure the AP queues to be used by the three guests so that the host can not
775 three guests and to provide an interface to the vfio_ap driver for
[all …]
|
| /linux/fs/fuse/ |
| H A D | Kconfig | 37 The Virtio Filesystem allows guests to mount file systems from the
40 If you want to share files between guests or with the host, answer Y
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-hypervisor-xen | 26 and all other guests. Only available to
27 privileged guests.
|
| /linux/Documentation/admin-guide/mm/damon/ |
| H A D | reclaim.rst | 22 memory to host, and the host reallocates the reported memory to other guests.
24 guests could be not so memory-frugal, mainly because some kernel subsystems and
26 guests could report only small amount of memory as free to host, results in
28 guests could mitigate this problem.
|
| /linux/include/xen/interface/hvm/ |
| H A D | start_info.h | 10 * Start of day structure passed to PVH guests and to HVM guests in %ebx.
82 * memory map is optional and so guests that understand version 1
|
| /linux/include/xen/arm/ |
| H A D | interface.h | 35 * Xen so that we can have one ABI that works for 32 and 64 bit guests.
59 /* Maximum number of virtual CPUs in multi-processor guests. */
|
| /linux/Documentation/virt/hyperv/ |
| H A D | vpci.rst | 43 guests as VMBus devices via the standard VMBus "offer"
77 created for Windows guests, and that can be ill-suited for
78 Linux guests due to differences in the overall structure of
197 hyperv.c) applies to Hyper-V and Linux guests running on x86
290 In Hyper-V guests these standard functions map to functions
|