Lines Matching refs:structure

254 memory slot.  Ensure the entire structure is cleared to avoid padding
331 See KVM_GET_REGS for the data structure.
862 See KVM_GET_VCPU_EVENTS for the data structure.
909 See KVM_GET_DEBUGREGS for the data structure. The flags field is unused
1237 Userspace invokes KVM_GET_SUPPORTED_CPUID by passing a kvm_cpuid2 structure
1295 If any additional field gets added to this structure later on, a bit for that
1363 See KVM_ASSIGN_PCI_DEVICE for the data structure. Only assigned_dev_id is
1422 See KVM_ASSIGN_DEV_IRQ for the data structure. The target device is specified
1697 See KVM_ASSIGN_DEV_IRQ for the data structure.  The target device is specified
1763 the argument structure.
2060 that the size of the access is variable, as the kvm_regs structure
2062 value in the kvm_regs structure seen as a 32bit array.
2132 userspace.  The host will set a flag in the pvclock structure that is checked
2133 from the soft lockup watchdog.  The flag is part of the pvclock structure that
2135 field of the pvclock_vcpu_time_info structure.  It will be set exclusively by
2207 KVM_CREATE_PIT2. The state is returned in the following structure:
2245 This populates and returns a structure describing the features of
2250 The structure contains some global information, followed by an
2696 handling guest debug events. There are two parts to the structure, the
2719 The second part of the structure is architecture specific and
2729 structure containing architecture specific debug information.
2767 structure with the 'nent' field indicating the number of entries in
2813 Parameters are specified via the following structure:
2973 and introspection. The parameter structure contains the address of a
3032 5. The kvm_run structure
3035 Application code obtains a pointer to the kvm_run structure by
3039 looking up structure members.
3355 Userspace can query the validity of the structure by checking
3360 Please note that the kernel is allowed to use the kvm_run structure as the