From: David Hildenbrand <david@redhat.com>
To: kvm@vger.kernel.org
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Sebastian Mitterle <smitterl@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, David Hildenbrand <david@redhat.com>
Subject: [kvm-unit-tests PATCH v1 0/2] s390x: firq: floating interrupt test
Date: Thu, 2 Dec 2021 10:58:41 +0100 [thread overview]
Message-ID: <20211202095843.41162-1-david@redhat.com> (raw)
From patch #2:
"
We had a KVM BUG fixed by kernel commit a3e03bc1368c ("KVM: s390: index
kvm->arch.idle_mask by vcpu_idx"), whereby a floating interrupt might get
stuck forever because a CPU in the wait state would not get woken up.
The issue can be triggered when CPUs are created in a nonlinear fashion,
such that the CPU address ("core-id") and the KVM cpu id don't match.
So let's start with a floating interrupt test that will trigger a
floating interrupt (via SCLP) to be delivered to a CPU in the wait state.
"
David Hildenbrand (2):
s390x: make smp_cpu_setup() return 0 on success
s390x: firq: floating interrupt test
lib/s390x/smp.c | 1 +
s390x/Makefile | 1 +
s390x/firq.c | 141 ++++++++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 10 ++++
4 files changed, 153 insertions(+)
create mode 100644 s390x/firq.c
--
2.31.1
next reply other threads:[~2021-12-02 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:58 David Hildenbrand [this message]
2021-12-02 9:58 ` [kvm-unit-tests PATCH v1 1/2] s390x: make smp_cpu_setup() return 0 on success David Hildenbrand
2021-12-02 10:30 ` Thomas Huth
2021-12-02 10:33 ` Claudio Imbrenda
2021-12-02 11:28 ` Janosch Frank
2021-12-02 9:58 ` [kvm-unit-tests PATCH v1 2/2] s390x: firq: floating interrupt test David Hildenbrand
2021-12-02 11:01 ` Claudio Imbrenda
2021-12-02 11:13 ` David Hildenbrand
2021-12-02 11:26 ` David Hildenbrand
2021-12-02 12:07 ` Claudio Imbrenda
2021-12-02 12:24 ` David Hildenbrand
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=20211202095843.41162-1-david@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=smitterl@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox