summaryrefslogtreecommitdiffstats
path: root/arch/s390/include/asm/sclp.h
diff options
context:
space:
mode:
authorDavid Hildenbrand <dahi@linux.vnet.ibm.com>2014-02-21 08:59:59 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2014-05-16 14:57:28 +0200
commit4953919feedaeb6d0161ecea920c35d1d1f639d3 (patch)
treef62ccaca28067e90562b6231f0e2dfac55f5a24b /arch/s390/include/asm/sclp.h
parentd26b8655f088ac6e972fd8f016b8dfa7cc1b9e5a (diff)
downloadop-kernel-dev-4953919feedaeb6d0161ecea920c35d1d1f639d3.zip
op-kernel-dev-4953919feedaeb6d0161ecea920c35d1d1f639d3.tar.gz
KVM: s390: interpretive execution of SIGP EXTERNAL CALL
If the sigp interpretation facility is installed, most SIGP EXTERNAL CALL operations will be interpreted instead of intercepted. A partial execution interception will occurr at the sending cpu only if the target cpu is in the wait state ("W" bit in the cpuflags set). Instruction interception will only happen in error cases (e.g. cpu addr invalid). As a sending cpu might set the external call interrupt pending flags at the target cpu at every point in time, we can't handle this kind of interrupt using our kvm interrupt injection mechanism. The injection will be done automatically by the SIE when preparing the start of the target cpu. Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> CC: Thomas Huth <thuth@linux.vnet.ibm.com> [Adopt external call injection to check for sigp interpretion] Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'arch/s390/include/asm/sclp.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud