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

/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
A D	vmm.h	311 #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/Documentation/security/
A D	snp-tdx-threat-model.rst	57 (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/Documentation/admin-guide/hw-vuln/
A D	cross-thread-rsb.rst	14 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
A D	multihit.rst	39 Privileged software, including OS and virtual machine managers (VMM), are in
/linux/Documentation/virt/hyperv/
A D	coco.rst	8 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
A D	overview.rst	11 encompass both the hypervisor and the VMM service without making a
/linux/Documentation/arch/x86/
A D	intel_txt.rst	46 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
A D	xstate.rst	174 components. These options are not presumed to support any particular VMM.
A D	sva.rst	246 ENQCMD can be used from within a guest VM. In these cases, the VMM helps
/linux/Documentation/virt/kvm/devices/
A D	vcpu.rst	225 From the source VMM process: 237 From the destination VMM process:
/linux/Documentation/arch/arm64/
A D	cpu-hotplug.rst	56 For a virtual machine, the VMM (e.g. Qemu) plays the part of firmware.
/linux/Documentation/networking/device_drivers/ethernet/intel/
A D	fm10k.rst	125 KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
A D	ixgbe.rst	540 Linux KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM.
/linux/drivers/virtio/
A D	Kconfig	57 drivers over PCI. This requires that your VMM has appropriate PCI
/linux/Documentation/virt/coco/
A D	sev-guest.rst	60 /* bits[63:32]: VMM error code, bits[31:0] firmware error code (see psp-sev.h) */
/linux/security/
A D	Kconfig	133 confidence that their hardware is running the VMM or kernel that
/linux/Documentation/virt/kvm/x86/
A D	amd-memory-encryption.rst	402 After completion of SEND_START, but before SEND_FINISH, the source VMM can issue the
/linux/Documentation/core-api/
A D	swiotlb.rst	39 and VMM. For the host to do I/O on behalf of the guest, the I/O must be
/linux/Documentation/virt/kvm/
A D	api.rst	5573 will always be fixed in the VMM regardless of where it is mapped 7539 instead of KVM_CREATE_IRQCHIP if the userspace VMM wishes to emulate the 7923 KVM_CAP_SGX_ATTRIBUTE enables a userspace VMM to grant a VM access to one or 7987 hibernation of the host; however the VMM needs to manually save/restore the 7995 When enabled the VMM may make use of the ``KVM_ARM_MTE_COPY_TAGS`` ioctl to 8010 upgrading the VMM process without interrupting the guest. 8150 When userspace sets KVM_X86_NOTIFY_VMEXIT_ENABLED bit in args[0], VMM will 8702 the dirty bitmap should be the very last thing that the VMM does before 8703 considering the state as complete. VMM needs to ensure that the dirty 8771 specifically enabled (by the guest making the hypercall, causing the VMM [all …]
/linux/arch/x86/
A D	Kconfig	908 some attacks from the VMM.

Completed in 58 milliseconds

Last Index update Fri Aug 22 08:59:00 CST 2025