| commit | f1cbfe6a736cf5a676fcdafcafdeb24125358c4e | |
| author | David Hildenbrand <david@redhat.com> | |
| Thu, 28 Sep 2017 20:36:47 +0000 (28 22:36 +0200) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Fri, 20 Oct 2017 11:32:10 +0000 (20 13:32 +0200) | ||
| tree | f50863fa3f4b855a103a436fb02cc47bb6f29a56 | treesnapshot (tar.gz zip) |
| parent | 83f7f32901c630f4fc01acd0d9082da466b17102 | commitdiff |
s390x/tcg: handle WAIT PSWs during interrupt injection
If we encounter a WAIT PSW, we have to halt immediately. Using
cpu_loop_exit() at this point feels wrong. Simply leaving
cs->exception_index set doesn't result in an immediate stop.
This is also necessary to properly handle SIGP STOP interrupts later.
The CPU_INTERRUPT_HALT will be processed immediately and properly set
the CPU to halted (also resetting cs->exception_index to EXCP_HLT)
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928203708.9376-10-david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
If we encounter a WAIT PSW, we have to halt immediately. Using
cpu_loop_exit() at this point feels wrong. Simply leaving
cs->exception_index set doesn't result in an immediate stop.
This is also necessary to properly handle SIGP STOP interrupts later.
The CPU_INTERRUPT_HALT will be processed immediately and properly set
the CPU to halted (also resetting cs->exception_index to EXCP_HLT)
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928203708.9376-10-david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| target/s390x/excp_helper.c | diffblobblamehistory |