Home
last modified time | relevance | path

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

/Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
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-v6.6/Documentation/admin-guide/hw-vuln/
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
Dmultihit.rst39 Privileged software, including OS and virtual machine managers (VMM), are in
/Linux-v6.6/Documentation/arch/x86/
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
Dxstate.rst174 components. These options are not presumed to support any particular VMM.
Dsva.rst246 ENQCMD can be used from within a guest VM. In these cases, the VMM helps
/Linux-v6.6/Documentation/virt/kvm/devices/
Dvcpu.rst225 From the source VMM process:
237 From the destination VMM process:
/Linux-v6.6/drivers/virtio/
DKconfig57 drivers over PCI. This requires that your VMM has appropriate PCI
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/intel/
Dfm10k.rst125 KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
Dixgbe.rst540 Linux KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM.
/Linux-v6.6/Documentation/virt/coco/
Dsev-guest.rst60 /* bits[63:32]: VMM error code, bits[31:0] firmware error code (see psp-sev.h) */
/Linux-v6.6/security/
DKconfig101 confidence that their hardware is running the VMM or kernel that
/Linux-v6.6/Documentation/virt/hyperv/
Doverview.rst11 encompass both the hypervisor and the VMM service without making a
/Linux-v6.6/Documentation/virt/kvm/x86/
Damd-memory-encryption.rst370 After completion of SEND_START, but before SEND_FINISH, the source VMM can issue the
/Linux-v6.6/Documentation/virt/kvm/
Dapi.rst7132 instead of KVM_CREATE_IRQCHIP if the userspace VMM wishes to emulate the
7514 KVM_CAP_SGX_ATTRIBUTE enables a userspace VMM to grant a VM access to one or
7572 VMM before creating any VCPUs to allow the guest access. Note that MTE is only
7578 hibernation of the host; however the VMM needs to manually save/restore the
7586 When enabled the VMM may make use of the ``KVM_ARM_MTE_COPY_TAGS`` ioctl to
7601 upgrading the VMM process without interrupting the guest.
7727 When userspace sets KVM_X86_NOTIFY_VMEXIT_ENABLED bit in args[0], VMM will
8227 the dirty bitmap should be the very last thing that the VMM does before
8228 considering the state as complete. VMM needs to ensure that the dirty
8295 specifically enabled (by the guest making the hypercall, causing the VMM
[all …]
/Linux-v6.6/arch/x86/
DKconfig893 some attacks from the VMM.