Lines Matching full:capability

75   Capability: which KVM extension provides this ioctl.  Can be 'basic',
80       support this ioctl, there's no capability bit to check its
97 Capability: basic
113 Capability: basic
134 Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
169 Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
187 Capability: basic
200 Capability: basic
211 Capability: basic
239 same partition.)  The KVM_CAP_PPC_SMT capability indicates the number
257 Capability: basic
281 the KVM_CAP_MULTI_ADDRESS_SPACE capability.
286 Capability: basic
297 Capability: basic
314 Capability: basic
344 Capability: basic
357 Capability: basic
385 Capability: basic
397 Capability: basic
421 Capability: basic
481 Capability: basic
492 Capability: basic (vcpu), KVM_CAP_GET_MSR_FEATURES (system)
529 Capability: basic
545 Capability: basic
574 Capability: basic
597 Capability: basic
623 Capability: basic
649 Capability: KVM_CAP_IRQCHIP, KVM_CAP_S390_IRQCHIP (s390)
664 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
670 Capability: KVM_CAP_IRQCHIP
691 capability is present (or unless it is not using the in-kernel irqchip,
724 Capability: KVM_CAP_IRQCHIP
746 Capability: KVM_CAP_IRQCHIP
768 Capability: KVM_CAP_XEN_HVM
793 Capability: KVM_CAP_ADJUST_CLOCK
823 Capability: KVM_CAP_ADJUST_CLOCK
842 Capability: KVM_CAP_VCPU_EVENTS
941 Capability: KVM_CAP_VCPU_EVENTS
980 Capability: KVM_CAP_DEBUGREGS
999 Capability: KVM_CAP_DEBUGREGS
1013 Capability: KVM_CAP_USER_MEM
1038 if this capability is supported by the architecture.
1043 KVM_CAP_MULTI_ADDRESS_SPACE capability.  Slots in separate address spaces
1059 use it.  The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1063 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1075 Capability: KVM_CAP_SET_TSS_ADDR
1094 Capability: KVM_CAP_ENABLE_CAP, KVM_CAP_ENABLE_CAP_VM
1107 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1114 The capability that is supposed to get enabled.
1133 Capability: KVM_CAP_MP_STATE
1175 Capability: KVM_CAP_MP_STATE
1195 Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1218 Capability: KVM_CAP_SET_BOOT_CPU_ID
1231 Capability: KVM_CAP_XSAVE
1246 Capability: KVM_CAP_XSAVE
1261 Capability: KVM_CAP_XCRS
1285 Capability: KVM_CAP_XCRS
1309 Capability: KVM_CAP_EXT_CPUID
1390 Capability: KVM_CAP_PPC_GET_PVINFO
1417 Capability: KVM_CAP_IRQ_ROUTING
1459   KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1460   the device ID.  If this capability is not available, userspace should
1484 feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
1504 Capability: KVM_CAP_TSC_CONTROL
1516 Capability: KVM_CAP_GET_TSC_KHZ
1529 Capability: KVM_CAP_IRQCHIP
1557 Capability: KVM_CAP_IRQCHIP
1572 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
1578 Capability: KVM_CAP_IOEVENTFD
1621 Capability: KVM_CAP_SW_TLB
1654 Capability: KVM_CAP_SPAPR_TCE
1663 and provides a scatter/gather capability for PAPR virtual I/O.
1690 Capability: KVM_CAP_PPC_RMA
1715 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
1723 Capability: KVM_CAP_USER_NMI
1749 Capability: KVM_CAP_S390_UCONTROL
1769 Capability: KVM_CAP_S390_UCONTROL
1789 Capability: KVM_CAP_S390_UCONTROL
1806 Capability: KVM_CAP_ONE_REG
2102 Capability: KVM_CAP_ONE_REG
2119 Capability: KVM_CAP_KVMCLOCK_CTRL
2140 Capability: KVM_CAP_SIGNAL_MSI
2159   KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2160   the device ID.  If this capability is not available, userspace
2168 feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
2175 Capability: KVM_CAP_PIT2
2207 Capability: KVM_CAP_PIT_STATE2
2232 Capability: KVM_CAP_PIT_STATE2
2246 Capability: KVM_CAP_PPC_GET_SMMU_INFO
2316 Capability: KVM_CAP_IRQFD
2353 Capability: KVM_CAP_PPC_ALLOC_HTAB
2362 virtualization.  Otherwise the capability doesn't exist and the ioctl
2389 Capability: basic
2432 Capability: KVM_CAP_PPC_HTAB_FD
2486 Capability: KVM_CAP_DEVICE_CTRL
2517 Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
2545 Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
2561 Capability: basic
2598 Capability: basic
2622 Capability: basic
2642 Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
2684 Capability: KVM_CAP_PPC_RTAS
2703 Capability: KVM_CAP_SET_GUEST_DEBUG
2753 Capability: KVM_CAP_EXT_EMUL_CPUID
2823 Capability: KVM_CAP_S390_MEM_OP
2869 Capability: KVM_CAP_S390_SKEYS
2900 Capability: KVM_CAP_S390_SKEYS
2927 Capability: KVM_CAP_S390_INJECT_IRQ
2982 Capability: KVM_CAP_S390_IRQ_STATE
3016 Capability: KVM_CAP_S390_IRQ_STATE
3053 Capability: KVM_CAP_X86_SMM
3063 Capability: KVM_CAP_PPC_MULTITCE
3067 This capability means the kernel is capable of handling hypercalls
3084 This capability is always enabled.
3088 Capability: KVM_CAP_SPAPR_TCE_64
3097 This capability uses extended struct in ioctl interface:
3120 Capability: KVM_CAP_REINJECT_CONTROL
3144 Capability: KVM_CAP_PPC_RADIX_MMU or KVM_CAP_PPC_HASH_MMU_V3
3175 Capability: KVM_CAP_PPC_RADIX_MMU
3209 Capability: KVM_CAP_SPAPR_RESIZE_HPT
3262 Capability: KVM_CAP_SPAPR_RESIZE_HPT
3304 Capability: KVM_CAP_MCE
3316 Capability: KVM_CAP_MCE
3323          -EINVAL if requested MCE capability is not supported.
3334 Capability: KVM_CAP_MCE
3367 Capability: KVM_CAP_S390_CMMA_MIGRATION
3457 Capability: KVM_CAP_S390_CMMA_MIGRATION
3502 Capability: KVM_CAP_PPC_GET_CPU_CHAR
3548 Capability: basic
3564 Capability: basic
3587 Capability: basic
3598 Capability: KVM_CAP_HYPERV_EVENTFD
3630 Capability: KVM_CAP_NESTED_STATE
3676 Capability: KVM_CAP_NESTED_STATE
4075   Target: whether this is a per-vcpu or per-vm capability.
4077   Parameters: what parameters are accepted by the capability.
4090 This capability enables interception of OSI hypercalls that otherwise would
4095 When this capability is enabled, KVM_EXIT_OSI can occur.
4105 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
4115 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
4168 This capability enables support for handling of channel I/O instructions.
4173 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
4176 Note that even though this capability is enabled per-vcpu, the complete
4186 This capability enables or disables the delivery of interrupts through the
4195 When this capability is enabled, KVM_EXIT_EPR can occur.
4203 This capability connects the vcpu to an in-kernel MPIC device.
4212 This capability connects the vcpu to an in-kernel XICS device.
4220 This capability enables the in-kernel irqchip for s390. Please refer to
4229 This capability allows the use of the host Floating Point Unit by the guest. It
4242 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
4301   Parameters: what parameters are accepted by the capability.
4313 This capability controls whether individual sPAPR hypercalls (hcalls)
4318 before this capability was implemented.  If disabled, the kernel will
4333 This capability controls which SIGP orders will be handled completely in user
4334 space. With this capability enabled, all fast orders will be handled completely
4345 in the hardware prior to interception). If this capability is not enabled, the
4363 This capability allows post-handlers for the STSI instruction. After
4397 This capability also enables in kernel routing of interrupt requests;
4442 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
4448 This capability can be enabled dynamically even if VCPUs were already
4473 Enabling this capability on a VM provides userspace with a way to set
4478 be 0.  A successful call to enable this capability will result in
4479 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
4480 subsequently queried for the VM.  This capability is only supported by
4482 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
4490 With this capability a machine check exception in the guest address
4493 machine check handling routine. Without this capability KVM will
4507 Enabling this capability on a VM provides userspace with a way to no
4524 With this capability the KVM support for memory backing with 1m pages
4525 through hugetlbfs can be enabled for a VM. After the capability is
4531 this capability, the VM will not be able to run.
4538 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
4540 capability does not enable write permissions of this MSR for the guest.
4552 This capability, if KVM_CHECK_EXTENSION indicates that it is
4556 with the KVM_CAP_PPC_ENABLE_HCALL capability.
4561 This capability, if KVM_CHECK_EXTENSION indicates that it is
4567 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
4575 This capability, if KVM_CHECK_EXTENSION indicates that it is
4584 This capability, if KVM_CHECK_EXTENSION indicates that it is
4593 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
4599 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
4620 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
4626 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
4633 This capability indicates the supported architecture type of the guest, i.e. the
4636 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
4657 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
4680 number larger than 0 indicating the version of this capability is implemented
4699 Querying this capability returns a bitmap indicating the possible
4708 This capability enables a newer version of Hyper-V Synthetic interrupt
4717 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr.  Its
4720 capability is absent, userspace can still query this msr's value.
4727 This capability indicates if the flic device will be able to get/set the
4735 This capability indicates that the PSW is exposed via the kvm_run structure.
4741 This capability indicates that the user space memory used as guest mapping can
4749 This capability indicates that the user space memory used as guest mapping can
4757 This capability indicates that kvm will implement the interfaces to handle
4759 facility 82 should not be provided to the guest without this capability.
4765 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
4774 This capability indicates that userspace can specify (via the
4777 If KVM advertises this capability, userspace can only specify the ISS field for