diff options
| author | David Hildenbrand | 2020-09-18 10:51:22 +0200 |
|---|---|---|
| committer | Cornelia Huck | 2020-10-02 13:52:49 +0200 |
| commit | 20d143e2cab8b597bbdb7a15f123d9704fa8db18 (patch) | |
| tree | a9b77da036804108c9914a126497db49def401ee /hw/vfio | |
| parent | s390: guest support for diagnose 0x318 (diff) | |
| download | qemu-20d143e2cab8b597bbdb7a15f123d9704fa8db18.tar.gz qemu-20d143e2cab8b597bbdb7a15f123d9704fa8db18.tar.xz qemu-20d143e2cab8b597bbdb7a15f123d9704fa8db18.zip | |
s390x/tcg: Implement MONITOR CALL
Recent upstream Linux uses the MONITOR CALL instruction for things like
BUG_ON() and WARN_ON(). We currently inject an operation exception when
we hit a MONITOR CALL instruction - which is wrong, as the instruction
is not glued to specific CPU features.
Doing a simple WARN_ON_ONCE() currently results in a panic:
[ 18.162801] illegal operation: 0001 ilc:2 [#1] SMP
[ 18.162889] Modules linked in:
[...]
[ 18.165476] Kernel panic - not syncing: Fatal exception: panic_on_oops
With a proper implementation, we now get:
[ 18.242754] ------------[ cut here ]------------
[ 18.242855] WARNING: CPU: 7 PID: 1 at init/main.c:1534 [...]
[ 18.242919] Modules linked in:
[...]
[ 18.246262] ---[ end trace a420477d71dc97b4 ]---
[ 18.259014] Freeing unused kernel memory: 4220K
Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20200918085122.26132-1-david@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'hw/vfio')
0 files changed, 0 insertions, 0 deletions