From: Hendrik Brueckner <brueckner@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH] KVM: s390: log machine checks more aggressively
Date: Tue, 10 Mar 2026 14:05:42 +0100 [thread overview]
Message-ID: <abAXJhjxah6NQZQl@linux.ibm.com> (raw)
In-Reply-To: <20260309115904.7280-1-borntraeger@linux.ibm.com>
On Mon, Mar 09, 2026 at 12:59:04PM +0100, Christian Borntraeger wrote:
> 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: Hendrik Brueckner <brueckner@linux.ibm.com>
prev parent reply other threads:[~2026-03-10 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:59 [PATCH] KVM: s390: log machine checks more aggressively Christian Borntraeger
2026-03-09 13:25 ` Janosch Frank
2026-03-10 13:05 ` Hendrik Brueckner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abAXJhjxah6NQZQl@linux.ibm.com \
--to=brueckner@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.