Lines Matching refs:architecture

1572 data format and layout are the same as documented in the architecture manual.
1589 and layout are the same as documented in the architecture manual.
1870 to a variable with the respective size. There can be architecture agnostic
1871 and architecture specific registers. Each have their own range of operation
2641 to know about. The id field is an architecture specific identifier for a
2703 The top 16 bits of the control field are architecture specific control
2716 we need to ensure the guest vCPUs architecture specific registers are
2719 The second part of the structure is architecture specific and
2729 structure containing architecture specific debug information.
2857 architecture. The ioctl takes parameters via the kvm_s390_skeys struct.
2887 architecture. The ioctl takes parameters via the kvm_s390_skeys struct.
3069 More architecture-specific flags detailing state of the VCPU that may
3092 reasons.  Further architecture-specific information is available in
3101 to unknown reasons.  Further architecture-specific information is
3135 for which architecture specific information is returned.
3303 a system-level event using some architecture specific mechanism (hypercall
3306 the system-level event type. The 'flags' field describes architecture
3342 	 * struct kvm_sync_regs is architecture specific, as well as the
3356 kvm_valid_regs for specific bits. These bits are architecture specific