From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call orders in enabled wait
Date: Wed, 13 Jul 2022 13:36:17 +0200 [thread overview]
Message-ID: <20220713113621.14778-1-nrb@linux.ibm.com> (raw)
When a CPU is in enabled wait, it can still receive SIGP calls from
other CPUs.
Since this requires some special handling in KVM, we should have tests
for it. This has already revealed a KVM bug with ecall under PV, which
is why this test currently fails there.
Some refactoring is done as part of this series to reduce code
duplication.
Nico Boehr (4):
lib: s390x: add cleanup function for external interrupts
s390x: smp: move sigp calls with invalid cpu address to array
s390x: smp: use an array for sigp calls
s390x: smp: add tests for calls in wait state
lib/s390x/asm/interrupt.h | 1 +
lib/s390x/interrupt.c | 9 ++
s390x/smp.c | 190 +++++++++++++++++++++-----------------
3 files changed, 115 insertions(+), 85 deletions(-)
--
2.35.3
next reply other threads:[~2022-07-13 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 11:36 Nico Boehr [this message]
2022-07-13 11:36 ` [kvm-unit-tests PATCH v1 1/4] lib: s390x: add cleanup function for external interrupts Nico Boehr
2022-07-13 11:36 ` [kvm-unit-tests PATCH v1 2/4] s390x: smp: move sigp calls with invalid cpu address to array Nico Boehr
2022-07-13 11:36 ` [kvm-unit-tests PATCH v1 3/4] s390x: smp: use an array for sigp calls Nico Boehr
2022-07-13 11:36 ` [kvm-unit-tests PATCH v1 4/4] s390x: smp: add tests for calls in wait state Nico Boehr
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=20220713113621.14778-1-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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