| commit | 741a4ec186160b632b6e19d2ad9623bc0121ea5d | |
| author | David Hildenbrand <david@redhat.com> | |
| Thu, 28 Sep 2017 20:37:08 +0000 (28 22:37 +0200) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Fri, 20 Oct 2017 11:32:10 +0000 (20 13:32 +0200) | ||
| tree | ef51ed709f0a17273b1034347cb5bba9f3f57b6c | treesnapshot (tar.gz zip) |
| parent | f74990a5d019751c545e9800a3376b6336e77d38 | commitdiff |
target/s390x: special handling when starting a CPU with WAIT PSW
When we try to start a CPU with a WAIT PSW, we have to take care that
TCG will actually try to continue executing instructions.
We must therefore really only unhalt the CPU if we don't have a WAIT
PSW. Also document the special order for restart interrupts, which
load a new PSW and change the state to operating.
To keep KVM working, simply don't have a look at the WAIT bit when
loading the PSW. Otherwise the behavior of a restart interrupt when
a CPU stopped would be changed.
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928203708.9376-31-david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
When we try to start a CPU with a WAIT PSW, we have to take care that
TCG will actually try to continue executing instructions.
We must therefore really only unhalt the CPU if we don't have a WAIT
PSW. Also document the special order for restart interrupts, which
load a new PSW and change the state to operating.
To keep KVM working, simply don't have a look at the WAIT bit when
loading the PSW. Otherwise the behavior of a restart interrupt when
a CPU stopped would be changed.
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928203708.9376-31-david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| target/s390x/cpu.c | diffblobblamehistory | |
| target/s390x/sigp.c | diffblobblamehistory |