| commit | 0f73c5b30b8ba6c0828608be496d2f59a5427539 | |
| author | Janosch Frank <frankja@linux.ibm.com> | |
| Thu, 19 Mar 2020 13:19:14 +0000 (19 09:19 -0400) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Wed, 29 Apr 2020 12:31:32 +0000 (29 14:31 +0200) | ||
| tree | 1f972b6b4ab69818fedb4cf41c5ecaa9026790d2 | treesnapshot (tar.gz zip) |
| parent | 7c713b8acb70fb61f9650f8a7702dec546752bb6 | commitdiff |
s390x: protvirt: SCLP interpretation
SCLP for a protected guest is done over the SIDAD, so we need to use
the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest
memory when reading/writing SCBs.
To not confuse the sclp emulation, we set 0x4000 as the SCCB address,
since the function that injects the sclp external interrupt would
reject a zero sccb address.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <20200319131921.2367-10-frankja@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
SCLP for a protected guest is done over the SIDAD, so we need to use
the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest
memory when reading/writing SCBs.
To not confuse the sclp emulation, we set 0x4000 as the SCCB address,
since the function that injects the sclp external interrupt would
reject a zero sccb address.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <20200319131921.2367-10-frankja@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| hw/s390x/sclp.c | diffblobblamehistory | |
| include/hw/s390x/sclp.h | diffblobblamehistory | |
| target/s390x/kvm.c | diffblobblamehistory |