kvm/s390/s390-pv.rst

26 the behavior of the SIE instruction. A new format 4 state description
48 of an instruction emulation by KVM, e.g. we can never inject a
63 Instruction emulation
65 With the format 4 state description for PVMs, the SIE instruction already
67 to interpret every instruction, but needs to hand some tasks to KVM;
71 Instruction Data Area (SIDA), the Interception Parameters (IP) and the
73 the instruction data, such as I/O data structures, are filtered.
74 Instruction data is copied to and from the SIDA when needed.  Guest
78 Only GR values needed to emulate an instruction will be copied into this
82 the bytes of the instruction text, but with pre-set register values
83 instead of the actual ones. I.e. each instruction always uses the same
84 instruction text, in order not to leak guest instruction text.
88 The Secure Instruction Data Area contains instruction storage
89 data. Instruction data, i.e. data being referenced by an instruction
90 like the SCCB for sclp, is moved via the SIDA. When an instruction is
92 this instruction to be moved to the guest via the two data areas
97 Instruction emulation interceptions
99 There are two types of SIE secure instruction intercepts: the normal
100 and the notification type. Normal secure instruction intercepts will
101 make the guest pending for instruction completion of the intercepted
102 instruction type, i.e. on SIE entry it is attempted to complete
103 emulation of the instruction with the data provided by KVM. That might
104 be a program exception or instruction completion.
107 changes due to guest instruction interpretation. Such an interception
108 is recognized, for example, for the store prefix instruction to provide
110 is ignored and execution continues as if the guest instruction had