KVM: s390: log machine checks more aggressively

Browse source

KVM will reinject machine checks that happen during guest activity.
From a host perspective this machine check is no longer visible
and even for the guest, the guest might decide to only kill a
userspace program or even ignore the machine check.
As this can be a disruptive event nevertheless, we should log this
not only in the VM debug event (that gets lost after guest shutdown)
but also on the global KVM event as well as syslog.
Consolidate the logging and log with loglevel 2 and higher.

Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Acked-by: Janosch Frank <frankja@linux.ibm.com>
Acked-by: Hendrik Brueckner <brueckner@linux.ibm.com>

...

This commit is contained in:

Christian Borntraeger 2026-03-06 11:25:40 +01:00

parent 0c6294d98a

commit 1ca90f4ae5

3 changed files with 6 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

arch/s390/kvm/interrupt.c

View file

1

arch/s390/kvm/kvm-s390.c

View file

1

arch/s390/kvm/vsie.c

View file