Home
last modified time | relevance | path

Searched refs:VMM (Results 1 – 24 of 24) sorted by relevance

/linux-6.15/Documentation/translations/zh_CN/security/
H A Dsnp-tdx-threat-model.rst53 全管理员的可信中介。宿主机侧的虚拟机监视器（VMM）通常由传统VMM功能的一个子集
66 | Host VMM |<---->| |
114 （这可能包括传统虚拟机监视器VMM的部分组件或全部），由于其较大的软件攻击面，
115 通常被置于CoCo VM TCB之外。需要注意的是，这并不意味着宿主机或VMM是故意恶意的，
135 | CoCo security |<--->| Host/Host-side VMM |
165 直接内存访问（DMA）接口、访问PCI配置空间、特定于虚拟机管理程序（VMM）的超调用
166 （指向主机端VMM）、访问共享内存页、主机允许注入到访客内核的中断，以及特定于
/linux-6.15/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
H A Dvmm.h311 #define VMM_MAP_ITER(VMM,PT,PTEI,PTEN,MAP,FILL,BASE,SIZE,NEXT) do { \ argument
325 VMM_SPAM(VMM, "ITER %08x %08x PTE(s)", PTEI, (u32)_ptes); \
327 FILL(VMM, PT, PTEI, _ptes, MAP, _addr); \
334 #define VMM_MAP_ITER_MEM(VMM,PT,PTEI,PTEN,MAP,FILL) \ argument
335 VMM_MAP_ITER(VMM,PT,PTEI,PTEN,MAP,FILL, \
339 #define VMM_MAP_ITER_DMA(VMM,PT,PTEI,PTEN,MAP,FILL) \ argument
340 VMM_MAP_ITER(VMM,PT,PTEI,PTEN,MAP,FILL, \
342 #define VMM_MAP_ITER_SGL(VMM,PT,PTEI,PTEN,MAP,FILL) \ argument
343 VMM_MAP_ITER(VMM,PT,PTEI,PTEN,MAP,FILL, \
/linux-6.15/Documentation/security/
H A Dsnp-tdx-threat-model.rst57 (VMM) typically consists of a subset of traditional VMM features and
72 | Host VMM |<---->| |
130 traditional VMM or all of it), which is typically placed outside of the
132 that this doesn’t imply that the host or VMM are intentionally
154 | CoCo security |<--->| Host/Host-side VMM |
172 While it is true that the host (and host-side VMM) requires some level of
194 and DMA interfaces, access to PCI configuration space, VMM-specific
195 hypercalls (towards Host-side VMM), access to shared memory pages,
/linux-6.15/Documentation/admin-guide/hw-vuln/
H A Dcross-thread-rsb.rst14 thread. However, KVM does allow a VMM to prevent exiting guest mode when
86 attempts to transition out of C0. A VMM can use the KVM_CAP_X86_DISABLE_EXITS
H A Dmultihit.rst39 Privileged software, including OS and virtual machine managers (VMM), are in
H A Drsb.rst125 only in the OS/VMM for OSes that enable SMEP. To do this, such
/linux-6.15/Documentation/arch/arm64/
H A Darm-cca.rst46 either by the VMM or by a `boot loader` run in the Realm before Linux:
64 VMM will remove the physical pages from the protected mapping and
H A Dcpu-hotplug.rst56 For a virtual machine, the VMM (e.g. Qemu) plays the part of firmware.
/linux-6.15/Documentation/virt/hyperv/
H A Dcoco.rst8 face of a hypervisor/VMM that has been compromised and may behave maliciously.
72 and must be trusted by the guest OS. By implication, the hypervisor/VMM must
132 happens in the paravisor in the guest context (instead of the hypervisor/VMM
141 hypervisor/VMM. This is done via callbacks invoked from
H A Doverview.rst11 encompass both the hypervisor and the VMM service without making a
/linux-6.15/Documentation/arch/x86/
H A Dintel_txt.rst46 Trusted Boot (tboot) is an open source, pre-kernel/VMM module that
48 kernel/VMM.
54 Tboot currently supports launching Xen (open source VMM/hypervisor
H A Dxstate.rst174 components. These options are not presumed to support any particular VMM.
H A Dsva.rst246 ENQCMD can be used from within a guest VM. In these cases, the VMM helps
/linux-6.15/Documentation/userspace-api/
H A Diommufd.rst95 multiple physical IOMMUs, in which case the VMM will dispatch the requests
104 the "dispatch" naturally instead of VMM trappings.
110 that VMM assigns to the device for a translation channel/port of the vIOMMU,
114 in a Confidential Compute Architecture. A VMM should create a vDEVICE object
/linux-6.15/Documentation/virt/kvm/devices/
H A Dvcpu.rst227 From the source VMM process:
239 From the destination VMM process:
/linux-6.15/Documentation/networking/device_drivers/ethernet/intel/
H A Dfm10k.rst125 KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
H A Dixgbe.rst540 Linux KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM.
/linux-6.15/drivers/virtio/
H A DKconfig57 drivers over PCI. This requires that your VMM has appropriate PCI
/linux-6.15/Documentation/virt/coco/
H A Dsev-guest.rst60 /* bits[63:32]: VMM error code, bits[31:0] firmware error code (see psp-sev.h) */
/linux-6.15/security/
H A DKconfig159 confidence that their hardware is running the VMM or kernel that
/linux-6.15/Documentation/virt/kvm/x86/
H A Damd-memory-encryption.rst402 After completion of SEND_START, but before SEND_FINISH, the source VMM can issue the
/linux-6.15/Documentation/core-api/
H A Dswiotlb.rst39 and VMM. For the host to do I/O on behalf of the guest, the I/O must be
/linux-6.15/Documentation/virt/kvm/
H A Dapi.rst5583 will always be fixed in the VMM regardless of where it is mapped
7636 instead of KVM_CREATE_IRQCHIP if the userspace VMM wishes to emulate the
8021 KVM_CAP_SGX_ATTRIBUTE enables a userspace VMM to grant a VM access to one or
8067 hibernation of the host; however the VMM needs to manually save/restore the
8075 When enabled the VMM may make use of the ``KVM_ARM_MTE_COPY_TAGS`` ioctl to
8090 upgrading the VMM process without interrupting the guest.
8237 When userspace sets KVM_X86_NOTIFY_VMEXIT_ENABLED bit in args[0], VMM will
8378 the dirty bitmap should be the very last thing that the VMM does before
8379 considering the state as complete. VMM needs to ensure that the dirty
8867 specifically enabled (by the guest making the hypercall, causing the VMM
[all …]
/linux-6.15/arch/x86/
H A DKconfig904 some attacks from the VMM.