Searched full:guests (Results 1 – 25 of 526) sorted by relevance
12345678910>>...22
| /kernel/linux/linux-6.6/include/xen/interface/ |
| 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
|
| /kernel/linux/linux-5.10/include/xen/interface/ |
| 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
|
| /kernel/linux/linux-5.10/drivers/vhost/ |
| 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
|
| /kernel/linux/linux-6.6/drivers/xen/ |
| D | Kconfig | 106 For example, by reading and writing the "xenbus" file, guests
195 device backend driver without para-virtualized support for guests.
198 other guests.
215 PCI devices to other guests. If you select this to be a module, you
217 you want to make visible to other guests.
257 to other guests via a high-performance shared-memory interface.
259 if guests need generic access to SCSI devices.
315 Support for auto-translated physmap guests.
369 Require virtio for Xen guests to use grant mappings.
|
| /kernel/linux/linux-6.6/drivers/vhost/ |
| D | Kconfig | 53 for use with virtio-scsi guests
63 sockets for communicating with guests. The guests must have the
86 This option allows vhost to support guests with a different byte
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/xen/ |
| D | interface.h | 78 * bit guests. */
106 /* Maximum number of virtual CPUs in multi-processor guests. */
205 * for HVM and PVH guests, not all information in this structure is updated:
207 * - For HVM guests, the structures read include: fpu_ctxt (if
210 * - PVH guests are the same as HVM guests, but additionally use ctrlreg[3] to
261 * For PV(H) guests these fields are RO.
284 * For PV(H) guests these fields are RO.
335 * WO for hypervisor, RO for guests.
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/xen/ |
| D | interface.h | 78 * bit guests. */
106 /* Maximum number of virtual CPUs in multi-processor guests. */
202 * for HVM and PVH guests, not all information in this structure is updated:
204 * - For HVM guests, the structures read include: fpu_ctxt (if
207 * - PVH guests are the same as HVM guests, but additionally use ctrlreg[3] to
258 * For PV(H) guests these fields are RO.
281 * For PV(H) guests these fields are RO.
332 * WO for hypervisor, RO for guests.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/staging/unisys/Documentation/ABI/ |
| 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.
|
| /kernel/linux/linux-6.6/arch/x86/kvm/ |
| D | Kconfig | 14 operating systems inside virtual machines (guests).
95 Enables KVM guests to create SGX enclaves.
98 guests via a device node, e.g. /dev/sgx_vepc.
136 Provides KVM support for the hosting Xen HVM guests and
|
| /kernel/linux/linux-5.10/arch/mips/kvm/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | tdx.rst | 25 TDX guests behave differently from bare-metal and traditional VMX guests.
26 In TDX guests, otherwise normal instructions or memory accesses can cause
63 In general, the #GP MSRs should not be used in guests. Their use likely
67 The #VE MSRs are typically able to be handled by the hypervisor. Guests
135 TDX guests ensure that all guest memory has been "accepted" before memory
174 emulates the access. That is not possible in TDX guests because VMEXIT
175 will expose the register state to the host. TDX guests don't trust the host
|
| /kernel/linux/linux-6.6/Documentation/virt/kvm/x86/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| 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 …]
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| 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 …]
|
| 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
|
| /kernel/linux/linux-5.10/drivers/xen/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/virt/hyperv/ |
| D | overview.rst | 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
21 Linux guests communicate with Hyper-V in four different ways:
89 On arm64, Hyper-V supports guests with 4/16/64 Kbyte pages as
127 earlier versions may provide guests with ACPI tables that indicate
143 On x86/x64, Hyper-V supports 32-bit and 64-bit guests, and Linux
148 On arm64, Hyper-V supports only 64-bit guests.
|
| /kernel/linux/linux-5.10/fs/vboxsf/ |
| 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.
|
| /kernel/linux/linux-6.6/fs/vboxsf/ |
| 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.
|
| /kernel/linux/linux-6.6/arch/powerpc/kvm/ |
| D | Kconfig | 12 other operating systems inside virtual machines (guests).
117 guests that use hash MMU mode.
167 Old nested HV capable Linux guests have a bug where they don't
171 L2 guests.
|
| /kernel/linux/linux-6.6/arch/x86/boot/ |
| D | io.h | 24 * TDX guests override these to use hypercalls.
35 * TDX guests override these callbacks with TDX-specific helpers.
|
12345678910>>...22